| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, David Fetter <david(at)fetter(dot)org> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Hartmut Goebel <h(dot)goebel(at)goebel-consult(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-bugs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
| Date: | 2010-06-04 20:50:51 |
| Message-ID: | 0155C20B401CB4DEC19D6F03@[80.156.86.78] |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
--On 4. Juni 2010 15:19:42 -0400 Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> That would make the bug go away,
> rather than require users to use a special flag (and find out only after
> they were doing the reload).
Out of curiosity, why is this a "bug" now? We recommend migration
procedures always to use the pg_dump of the newer version because of many
reasons as clearly stated here:
<http://www.postgresql.org/docs/8.4/interactive/migration.html>
And wouldn't introducing backpatching such behavorial changes to pg_dump
violate our policy in *not* to change such things in minor releases? (think
of diff's against schema-only dumps and so on....).
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-06-04 20:53:36 | Re: superuser unable to modify settings of a system table |
| Previous Message | Robert Haas | 2010-06-04 20:41:08 | Re: superuser unable to modify settings of a system table |