Postgres Pro
Downloads
Home   >   mailing lists

Re: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)? - Mailing list pgsql-general

From Tom Lane
Subject Re: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)?
Date
Msg-id 6258.1267924384@sss.pgh.pa.us
Whole thread Raw
In response to Re: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)?  (Scott Ribe <scott_ribe@killerbytes.com>)
List pgsql-general
Tree view 
Scott Ribe <scott_ribe@killerbytes.com> writes:
>> OK, what probably happened was that the data was loaded okay and then
>> you got these errors from the commands that attempted to create unique
>> indexes.

> Isn't it also possible that she was not restoring into an empty database?

Maybe, but then she should have seen complaints about pre-existing
tables and so forth, too.

            regards, tom lane

pgsql-general by date:

Previous
From: Scott Ribe
Date:
Subject: Re: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)?
Next
From: Bruce Momjian
Date:
Subject: Re: non intuitive behaviour of DROP TABLE IF EXISTS