Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading
От | Tom Lane |
---|---|
Тема | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
Дата | |
Msg-id | 17059.1276183641@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: BUG #5488: pg_dump does not quote column names -> pg_restore
may fail when upgrading
Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
Список | pgsql-bugs |
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: > On 10/06/10 16:21, Robert Haas wrote: >> I do agree that the human readability of pg_dump is an asset in many >> situations - I have often dumped out the DDL for particular objects >> just to look at it, for example. However, I emphatically do NOT agree >> that leaving someone with a 500MB dump file (or, for some people on >> this list, a whole heck of a lot larger than that) that has to be >> manually edited to reload is a useful behavior. It's a huge pain in >> the neck. > Much easier to do a schema-only dump, edit that, and dump data separately. That gets you out of the huge-file-to-edit problem, but the performance costs of restoring a separate-data dump are a pretty serious disadvantage. We really should do something about that. regards, tom lane
В списке pgsql-bugs по дате отправления: