posted 16 years ago
Hi, I'm from the same place as madjaguar...
Thanks for your help so far; I think we're getting close to the answer.
I can see why you'd think from that stack trace that the database was locked, but that's not the case here. We're using PostgreSQL on the backend, and that error message means a previous statement within the current transaction has failed. In PostgreSQL, within a transaction, once a statement has failed, every subsequent statement until the next rollback will get that error.
I found the revelant information from the server log. Unfortunately, there is no stack trace for the initial error, which does appear to be due to the new unique constraint:
So the stack trace posted earlier (which I have snipped out here) is just fallout from the real problem, for which we don't have a stack trace.
Any ideas?
-Jonathan
[originally posted on jforum.net by jfuerth]