Re: PostgreSQL 9.1 pg_dump setval() sets wrong value - Mailing list pgsql-general

From Greg Donald
Subject Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Date
Msg-id CAO+WgCbnE=tQ2DsDb7a1kRQ0JksP8Mu6_eNaJXyxFsrEYChzDQ@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL 9.1 pg_dump setval() sets wrong value  (Scott Marlowe <scott.marlowe@gmail.com>)
Responses Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
List pgsql-general
> Are you
> sure that the sequence is being used to insert those values into the
> table?

When I insert a new row into either of the tables I previously
described, the sequence 'Current value' increments by one.  When I use
pg_dump to backup the database most of the setval() calls in my SQL
file have a '1', like this:

SELECT pg_catalog.setval('company_id_seq', 1, false);

Some do not have a '1', some are actually set correctly.


Thanks.


--
Greg Donald

pgsql-general by date:

Previous
From: hosuresh
Date:
Subject: Re: psql error: psql: symbol lookup error: psql: undefined symbol: PQconnectdbParams
Next
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value