Hello
On 2019-Apr-22, pavan95 wrote:
> Do you mean this to be a bug?
A bug fixed two years ago, yeah.
> My question is in my error log I'm getting query text for that corresponding
> "could not serialize access due to concurrent update" error failures. But
> can I get the other transaction which committed and which is responsible for
> this above serialization update?
You probably *can*, by ensuring that all transactions have sufficient
details in the log; you may be able to link the entries by PID or XID.
Not sure how easy that is.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services