Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 19:01:59
Message-ID: 4090.1325098919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> On Wednesday, December 28, 2011 7:51:24 am Greg Donald wrote:
>> 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

If that were the issue, Greg would be seeing pg_dump fail altogether,
not complete with bogus output. In any case, as that table says,
"id" is not a reserved word in Postgres.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message karthikeyan 2011-12-28 19:29:40 Unable to Increase the column which was part of Primary key
Previous Message Tom Lane 2011-12-28 19:00:10 Re: PostgreSQL 9.1 pg_dump setval() sets wrong value