Heh, I see. The sequence currval was set lower than what was already in
the table. It just so happened we had holes in our data for the values
it was selecting. Thanks for pointing that out!
Kris
Michael Fuhr wrote:
On Thu, Mar 24, 2005 at 04:45:02PM -0500, Kris Kiger wrote:
I'm positive no one else has been in the database. There are two of us
who work on it and we have been side by side all afternoon. The problem
appears to be purely internal to the database. I'm running more tests
as we speak and we are still recieving the same sporadic errors. It
works for a long amount of time and then the error occurs, but then
things work fine again for a while. The inconsistency is quite troubling.
What are the results of the following queries?
SELECT max(d_id) FROM hd;
SELECT * FROM hd_d_id_seq;
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
