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 | AANLkTikC6SWYcFQ6A1Xxu7Pr_9sIgBe9EtRT7FclQHoz@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading (Dimitri Fontaine <dfontaine@hi-media.com>) |
Ответы |
Re: BUG #5488: pg_dump does not quote column names -> pg_restore
may fail when upgrading
|
Список | pgsql-bugs |
On Fri, Jun 11, 2010 at 2:46 PM, Dimitri Fontaine <dfontaine@hi-media.com> wrote: >>>> 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! =A0It's a heck of a lot easier to fix the application than it is to >> doctor the dump output with vi. > > But of course you don't ever do that. What you do once the restore failed= on > you is fix the schema and the application before to upgrade. Presumably, you mean that YOU don't ever do that. What everybody else does is up to them, and there are plenty of people on this thread saying either (1) they don't want to do what you're proposing or (2) their application doesn't need fixing because it already quotes everything. --=20 Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-bugs по дате отправления: