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 15:23:19 -0400
Message-ID: <20190425192319.GA8081@alvherre.pgsql> (raw)
In-Reply-To: <20190425174738.GA31344@alvherre.pgsql>
On 2019-Apr-25, Alvaro Herrera wrote:
> Hello
>
> On 2019-Apr-22, pavan95 wrote:
>
> > Do you mean this to be a bug?
>
> A bug fixed two years ago, yeah.
Let me correct myself. What I fixed two years ago was some spurious
occurrences of the reported message. However, the same error message
can be returned in other circumstances, and I suspect many of them would
not be spurious. Therefore, my suggestion is:
1. if you're on a release older than the bugfix, then upgrade and try
again.
2. if you're already on a release with that problem fixed, then
investigate and to determine whether (some of?) the occassions on which
the error is raised are spurious.
3. if you find some occassions on which they are spurious, see if you
can do something to fix that (say, increment # of predicate locks in
postgresql.conf; maybe fix some other bug).
--
Á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: <20190425192319.GA8081@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