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

From: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>
Cc: "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:00:48
Message-ID: C7B848D0.D098C%scott_ribe@killerbytes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 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?

--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-03-07 01:13:04 Re: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)?
Previous Message Aleksandar Sosic 2010-03-06 23:16:16 postgresql 8.2 startup script