Magnus Hagander wrote: > On Thu, Jun 10, 2010 at 15:35, Stefan Kaltenbrunner > <ste...@kaltenbrunner.cc> wrote: > > Robert Haas wrote: > >> > >> On Thu, Jun 10, 2010 at 9:02 AM, Stefan Kaltenbrunner > >> <ste...@kaltenbrunner.cc> wrote: > >>> > >>> I for myself would be rather annoyed if we started quoting all column > >>> names > >>> in our dumps. This is seriously hampering readability and while it is > >>> already annoying that pg_dump output is slightly different from the > >>> original > >>> DDL used this would make it far worse. > >> > >> It's only been proposed to make it an option, not to shove it down > >> anyone's throat. > > > > that will pretty much defeat the purpose for most use cases i guess because > > people will dump with the defaults and only discover the problem after the > > fact. > > Well, if you dump in custom format, it could be useful to be able to > do this on pg_restore time. Not having followed this thread in detail, > but would that work? That would be a much more useful option...
I don't think so because much of the quoting has to be done in the backend, and it would be hard for pg_dump to munge the dump file before sending it to the backend --- it doesn't have enough knowledge, I am afraid. It could try targeting just new keywords, but I am worried that would cause more problems than it fixes. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
