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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
Cc: "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)?
Date: 2010-03-07 01:13:04
Message-ID: 6258.1267924384@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Scott Ribe <scott_ribe(at)killerbytes(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2010-03-07 01:49:29 Re: non intuitive behaviour of DROP TABLE IF EXISTS
Previous Message Scott Ribe 2010-03-07 01:00:48 Re: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)?