From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: pavan95 <pavan.postgresdba@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Too many serialization errors in production
Date: Thu, 25 Apr 2019 13:47:38 -0400
Message-ID: <20190425174738.GA31344@alvherre.pgsql> (raw)
In-Reply-To: <1555939076842-0.post@n3.nabble.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@2ndquadrant.com, pavan.postgresdba@gmail.com
Subject: Re: Too many serialization errors in production
In-Reply-To: <20190425174738.GA31344@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox