On Sun, Jun 6, 2010 at 2:53 PM, Dimitri Fontaine <dfonta...@hi-media.com> wrote: > Robert Haas <robertmh...@gmail.com> writes: >>> Well as Bruce said this option won't solve the OP's problem, unless the >>> application he's using for managing the backups do use the option. >> >> Well, that's a pretty trivial change to the backup script. +1 from me on >> providing a pg_dump option. > > The application still have to have been using the option in the past.
Well, if your point is that it's too late to help anyone upgrading from 8.3 to 8.4, then I agree with you. But we will likely add more keywords at some point in the future, and while providing an output format that quotes everything won't fix every potential problem, it might make life easier for some people. I certainly have had times where it would have saved me hassle and aggravation. I think as a community we can sometimes be a bit intolerant of people who don't do things exactly the right way and get themselves into trouble. I don't think we should tell people "there is a theoretical way that you could have avoided falling down that pit so it's all good" - we should try to build fences around the pits. There's no way we can future-proof pg_dump output completely because we don't know what we'll change in the future, but I don't think that makes it worthless to provide an option that makes it future-proof against one of the common causes of trouble. If I had a nickle for every time I read a bug report about a usability issue that has also bitten me, I'd have about two bucks. If I had another nickle for every time someone told one of those people their problem is their own fault, I would have about another four bucks. The fact that it's true doesn't mean that it's the best we can do. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs