Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

From: Greg Donald <gdonald(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Date: 2011-12-28 14:54:54
Message-ID: CAO+WgCbnE=tQ2DsDb7a1kRQ0JksP8Mu6_eNaJXyxFsrEYChzDQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2011-12-28 15:07:31 Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Previous Message hosuresh 2011-12-28 13:03:58 Re: psql error: psql: symbol lookup error: psql: undefined symbol: PQconnectdbParams