Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading
От | Robert Haas |
---|---|
Тема | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
Дата | |
Msg-id | AANLkTike3nTjMWur6NkZmJ7o7QG4qhg06SYF8SeJW7nL@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading
|
Список | pgsql-bugs |
On Wed, Jun 9, 2010 at 9:35 PM, Bruce Momjian <bruce@momjian.us> wrote: > Robert Haas wrote: >> > I think users would rather have the restore fail, and know right away >> > they have an issue, than to do the upgrade, and find out later that so= me >> > of their application queries fail and they need to run around fixing >> > them. ?(FYI, pg_upgrade would use the new pg_dump and would not fail.) >> > >> > In a way, the fact that the restore fails can be seen as a feature --- >> > they get the error before the go live on 8.4. ?(Yeah, I am serious.) >> >> Eeh, I've had this happen to me on earlier releases, and it didn't >> feel like a feature to me. =A0YMMV, of course. > > Would you have preferred later application failure? YES! It's a heck of a lot easier to fix the application than it is to doctor the dump output with vi. --=20 Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-bugs по дате отправления: