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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
