Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

On Wed, Dec 28, 2011 at 8:38 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:

> On Wed, Dec 28, 2011 at 10:20 AM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
> wrote:
>
> >
> > 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.
>

Well just tested using 9.1.1 pg_dump to dump an 8.4.9 database with table:
CREATE TABLE id_test (
id integer NOT NULL,
fld_1 text
);

Everything worked including:

SELECT pg_catalog.setval('id_test_id_seq', 5, true)

which represents the correct sequence value.

So something else is going on.

>
> merlin
>

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com