Re: Deprecating, and scheduling removal of, pg_dump's tar format. - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Deprecating, and scheduling removal of, pg_dump's tar format.
Date
Msg-id 20180727030950.GL27724@tamriel.snowman.net
Whole thread Raw
In response to Re: Deprecating, and scheduling removal of, pg_dump's tar format.  (Christophe Pettus <xof@thebuild.com>)
Responses Re: Deprecating, and scheduling removal of, pg_dump's tar format.  (Christophe Pettus <xof@thebuild.com>)
List pgsql-hackers
Greetings,

* Christophe Pettus (xof@thebuild.com) wrote:
> > On Jul 26, 2018, at 19:35, Peter Geoghegan <pg@bowt.ie> wrote:
> >
> > Why, specifically, would it make them unhappy?
>
> Forensic and archive backups in .tar format (which I know of users doing) would require a two-step restore process on
newerversions. 

Do you, perhaps, have any insight into why those users are currently
using the .tar format?

The use of temp files strikes me as a particularly good reason to do
away with that format as it can cause odd failure cases.

The other downside is that it's just more testing to be done to make
sure that we didn't break it, testing which every developer waits for
whenever they run the test suite.  Further, any changes in pg_dump that
could possibly impact the tar format also need to have tests written for
them to make sure that this particular format, that has no real
advantages or redeeming qualities over the other formats, continues to
work.

Thanks!

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Nico Williams
Date:
Subject: Re: How can we submit code patches that implement our (pending)patents?
Next
From: Tom Lane
Date:
Subject: Re: negative bitmapset member not allowed Error with partition pruning