| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Hartmut Goebel <h(dot)goebel(at)goebel-consult(dot)de>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
| Date: | 2010-06-10 15:58:15 |
| Message-ID: | 20100610155815.GG21875@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
* Stefan Kaltenbrunner (stefan(at)kaltenbrunner(dot)cc) wrote:
> well that is an argument for providing not only --schema-only and
> --data-only but rather three options one for the table definitions, one
> for the data and one for all the constraints and indexes. So basically
> what pg_dump is currently doing anyway but just exposed as flags.
There was a big/long thread on this on -hackers a while back.. Perhaps
we need to go back and figure out what happened. Have to admit, that's
one of the reason I like creating wiki pages for these kinds of, even
admittedly small, things. Easier to find than searching the archive,
ime. Of course, that'll probably change as more things get added to the
wiki. :)
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-06-10 16:00:59 | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
| Previous Message | Stephen Frost | 2010-06-10 15:56:31 | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |