From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com> |
Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <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:09:50 |
Message-ID: | 20180727030950.GL27724@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Christophe Pettus (xof(at)thebuild(dot)com) wrote:
> > On Jul 26, 2018, at 19:35, Peter Geoghegan <pg(at)bowt(dot)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 newer versions.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-07-27 03:14:45 | Re: negative bitmapset member not allowed Error with partition pruning |
Previous Message | Nico Williams | 2018-07-27 03:06:23 | Re: How can we submit code patches that implement our (pending) patents? |