From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | John R Pierce <pierce(at)hogranch(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14152: pg_dump does not take into account previous versions reserved keywords as column names |
Date: | 2016-05-20 18:25:02 |
Message-ID: | 54607.1463768702@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Fri, May 20, 2016 at 2:02 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
>> pg_dump and pg_dumpall are supposed to be able to dump all supported prior
>> versions, thats the documented procedure for updating... I contend this
>> *is* a bug. quote-all-identifiers is a workaround, for sure.
> If indeed the prescribed procedure is quote-all-identifiers I'd say we
> should at least update the docs.
Yeah, agreed. I'll put something in.
Alternatively, we could automatically turn on quote-all-identifiers when
dumping from a server of a different major version; but I imagine we'd
get complaints about that, too, since it's so seldom an issue.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2016-05-20 18:59:45 | Re: BUG #14152: pg_dump does not take into account previous versions reserved keywords as column names |
Previous Message | Michael Paquier | 2016-05-20 18:12:33 | Re: BUG #14152: pg_dump does not take into account previous versions reserved keywords as column names |