Re: Deprecating, and scheduling removal of, pg_dump's tar format.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Subject: Re: Deprecating, and scheduling removal of, pg_dump's tar format.
Date: 2018-07-27 03:46:11
Message-ID: 21877.1532663171@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Is there any real reason to retain it?

As I recall, the principal argument for having it to begin with was
that it's a "non proprietary" format that could be read without any
PG-specific tools. Perhaps the directory format could be said to
serve that purpose too, but if you were to try to collapse a directory
dump into one file for transportation, you'd have ... a tar dump.

I think a more significant question is what we'd get by removing it?
If you want to look around for features that are slightly less used
than other arguably-equivalent things, we must have hundreds of those.
Doesn't mean that those features have no user constituency.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-07-27 04:15:42 Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack
Previous Message Kyotaro HORIGUCHI 2018-07-27 03:37:02 Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack