From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Changing pg_dump default file format |
Date: | 2013-11-07 16:55:11 |
Message-ID: | 527BC5EF.1050002@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/07/2013 08:26 AM, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Thu, Nov 7, 2013 at 5:02 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> 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.
>
>> I'm a bit worried about it breaking peoples scripts as well, if they
>> pipe the output.
>
> Whether they pipe the output or not, this will break people's scripts.
> I agree it's a legacy behavior that we wouldn't choose again, but you
> could say that about an awful lot of things including much of the SQL
> standard. I think it's too late to consider this now.
We have certainly done worse in the past. 8.3 comes to mind. I am trying
to consider the future here, as we continue to grow. Why leave thorns
for the sake of leaving thorns?
Note:
Perfectly happy to spit out a, "NOTICE: The default format of pg_dump
will be changing in release X" for a release.
Joshua D. Drake
>
> regards, tom lane
>
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-11-07 17:18:26 | Re: alter_table regression test problem |
Previous Message | Harold Giménez | 2013-11-07 16:53:49 | Re: Changing pg_dump default file format |