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: "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-06 21:37:56
Message-ID: 4260.1267911476@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com> writes:
> Actually I got that type of error during the restore process( I used pg_dump --insert option when doing the dump). But the interesting thing is that even though it flagged as an error, those rows of inserts still made to the table with the correct bug_id. So I'm not too worried about it right now.
> I've always suspected that the database was inconsistent state.

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. So aside from the problem that your data is inconsistent,
you now also lack indexes. You probably ought to see about fixing
the duplications so that you can establish the indexes.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Aleksandar Sosic 2010-03-06 23:16:16 postgresql 8.2 startup script
Previous Message Dimitri Fontaine 2010-03-06 20:37:44 Re: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)?