From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, Greg Donald <gdonald(at)gmail(dot)com> |
Subject: | Re: PostgreSQL 9.1 pg_dump setval() sets wrong value |
Date: | 2011-12-28 16:38:12 |
Message-ID: | CAHyXU0yAS-SytFPfWXpwJk96ZKausC3MzGgt=F2M+e4y2nAxaA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Dec 28, 2011 at 10:20 AM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> wrote:
> On Wednesday, December 28, 2011 7:51:24 am Greg Donald wrote:
>> On Wed, Dec 28, 2011 at 9:30 AM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
> wrote:
>> > Wonder if it is related to this:
>> > http://archives.postgresql.org/pgsql-bugs/2011-11/msg00098.php
>>
>> None of my sequences are named 'new'. What do you mean?
>
> I was thinking of the more generic case. The problem with 'new' in the above bug
> is that it is a reserved word and the list of reserved words recognized by
> pg_dump changed in 9.0 or 9.1(?). If the table definitions you showed are correct
> you have sequence columns named id. id is in the list of reserved words also:
>
> http://www.postgresql.org/docs/9.1/static/sql-keywords-appendix.html
hm -- if sequences named 'id' are not dumping properly, I'd call that
a pretty significant bug.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-12-28 18:34:26 | Re: Re: psql error: psql: symbol lookup error: psql: undefined symbol: PQconnectdbParams |
Previous Message | Adrian Klaver | 2011-12-28 16:36:11 | Re: PostgreSQL 9.1 pg_dump setval() sets wrong value |