Hi,
> In PostgreSQL, 40001 is used for serialization failures due to MVCC
> issues, and 40P01 is used for serialization failures due to
> deadlocks. I think that many years back when PostgreSQL moved to
> MVCC it was judged important to differentiate between them with
> different SQLSTATE values
Hi,
> 40P01 is mentioned in the manual. See "A. PostgreSQL Error Codes" of
> Appendixes.
I meant "mentioned in the manual in the section about concurrency control".
Since I alluded to class 40 errors, I think it was safe to assume that I was
familiar with Appendix A...
Best,
Jon
--
Sent via
Jon Smark wrote:
> The manual mentions that SERIALIZABLE transactions may abort with
> error 40001, in which case the client application is supposed to
> retry the transaction. I've been stress testing an application
> by issuing lots of concurrent requests, and sure enough, every
> now and then
> The manual mentions that SERIALIZABLE transactions may abort with error 40001,
> in which case the client application is supposed to retry the transaction.
> I've been
> stress testing an application by issuing lots of concurrent requests, and
> sure enough,
> every now and then I get back tho
