From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Changing pg_dump default file format |
Date: | 2013-11-07 17:25:11 |
Message-ID: | CABUevExGSG_7=Z=8z2AxdG3hrD8Y8RrvT0ssNieW1Rc2GVqnaQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 7, 2013 at 5:53 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>
> On 11/07/2013 08:21 AM, Kevin Grittner wrote:
>
>>> I humbly request on behalf of those who manage production postgresql
>>> instances that we change the default backup file format from -Fp to -Fc.
>>
>>
>> -1 in the case that output goes to stdout. It might make sense for
>> when -f is specified. As a DBA, 90% of my usage of pg_dump was
>> piped to psql, with the rest split between data-only dumps for
>> individual tables and schema-only dumps. I think I used -Fc about
>> twice -- before I figured out how to do PITR-style backups.
>>
>
> PITR is wonderful, I use it all the time. It has exactly zero to do with
> what we are talking about. We are talking about pg_dump and its usefulness.
> Are you suggesting that we tell people to not use pg_dump and instead use
> PITR?
For backups, absolutely.
That is, assuming you mean "pg_basebackup -x", and not full
archive_command/full pitr setup.
That's still a separate argument, of course.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2013-11-07 17:39:52 | Re: Changing pg_dump default file format |
Previous Message | Andres Freund | 2013-11-07 17:18:26 | Re: alter_table regression test problem |