From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Changing pg_dump default file format |
Date: | 2013-11-08 02:29:08 |
Message-ID: | 527C4C74.60106@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/07/2013 06:33 PM, Joshua D. Drake wrote:
>
> On 11/07/2013 12:42 PM, Josh Berkus wrote:
>>
>> All,
>>
>> I'm amused at how this has become a "let's pile on everything which has
>> ever been missing in pg_dump into one thread".
>
> Well it has been broken longer than most of our utilities. Sorry...
> not broken but certainly not complete. It is to be expected.
>
>>
>> Agree with Tom that if we're going to create a new program name, we
>> should fix the pg_dumpall issue as well.
>>
>
> All I want to start is this simple fix. I don't know who is going to
> step up to work on pg_dump/all considering it is the bastard step
> child of the project. We only work on it when we absolutely have to
> (and CMD is just as guilty as the rest).
>
>
What you're asking for isn't a simple fix. Calling it one doesn't make
it so.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2013-11-08 03:01:11 | Re: Changing pg_dump default file format |
Previous Message | Craig Ringer | 2013-11-08 02:17:20 | Re: [v9.4] row level security |