| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | 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:00:45 |
| Message-ID: | 88f9fa94-5676-6102-b1c7-2be51d19c00f@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/26/2018 07:41 PM, Christophe Pettus 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.
I am a +1 for removing the format, though I would suggest we leave it as
a restore option (pg_restore) for at least two more major releases. It
is nice to get rid of cruft.
JD
>
> --
> -- Christophe Pettus
> xof(at)thebuild(dot)com
>
>
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
***** Unless otherwise stated, opinions are my own. *****
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nico Williams | 2018-07-27 03:06:23 | Re: How can we submit code patches that implement our (pending) patents? |
| Previous Message | Stephen Frost | 2018-07-27 03:00:37 | Re: How can we submit code patches that implement our (pending) patents? |