| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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 <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-06 18:40:19 |
| Message-ID: | 059FACA3-B478-494D-8A5B-FF56D407DD5A@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Jun 5, 2010, at 4:02 PM, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> I don't think "dumps must be human-readable" is an argument to reject
>> such a switch, as long as it's off by default. And I haven't seen
>> any
>> other valid argument either, so +1 from me.
>
> Well as Bruce said this option won't solve the OP's problem, unless
> the
> application he's using for managing the backups do use the option.
Well, that's a pretty trivial change to the backup script. +1 from me
on providing a pg_dump option.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-06-06 18:53:30 | Re: BUG #5488: pg_dump does not quote column names -> pg_restore may fail when upgrading |
| Previous Message | Craig Ringer | 2010-06-06 03:09:24 | Re: Re: BUG #5490: INSERT doesn't force cast from text to timestamp |