Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading
От | Stephen Frost |
---|---|
Тема | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
Дата | |
Msg-id | 20100610141836.GZ21875@tamriel.snowman.net обсуждение исходный текст |
Ответ на | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: BUG #5488: pg_dump does not quote column names -> pg_restore
may fail when upgrading
|
Список | pgsql-bugs |
* Magnus Hagander (magnus@hagander.net) wrote: > On Thu, Jun 10, 2010 at 15:35, Stefan Kaltenbrunner > <stefan@kaltenbrunner.cc> wrote: > > that will pretty much defeat the purpose for most use cases i guess bec= ause > > people will dump with the defaults and only discover the problem after = the > > fact. >=20 > 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... Personally, I feel that *both* would be useful, and I'd be unhappy with any implementation which didn't include both. That being said, the users that are likely to run into this problem will, imnsho, be much happier if we tell them "oh, just flip option X in your pg_dump" than "go edit the .sql file with vi and find where the problem cases are and fix them". Obviously, we should caveat our response that this will only fix the pg_dump/restore problem and that their applications may need to be fixed. Thanks, Stephen
В списке pgsql-bugs по дате отправления: