public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: [email protected]
To: Thom Brown <[email protected]>
Cc: pgsql-general mailing list <[email protected]>
Subject: Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ?
Date: Fri, 19 Jun 2026 09:06:12 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CAA-aLv4UZ9bOtEDbdeCa1KMmdgCxzaT-YQnEN=ZZ7LUQTp+GJw@mail.gmail.com>
<[email protected]>
On Thu, 2026-06-18 at 15:33 +0200, hubert depesz lubaczewski wrote:
> On Thu, Jun 18, 2026 at 02:07:36PM +0100, Thom Brown wrote:
> > Have you got anything in the logs that say "conflict with recovery"?
> > Also, I know you are just running count(*), but is there a transaction
> > being left open?
> > SELECT pid, state, xact_start, query
> > FROM pg_stat_activity
> > ORDER BY xact_start NULLS LAST;
> > Any 'idle in transaction' for too long?
> > What is max_standby_streaming_delay and hot_standby_feedback set to?
>
> No transactions were happening then. These are our "Disaster Recovery"
> instances, and they are generally unused.
>
> max_standby_streaming_delay is 10 minutes
> hot_standby_feedback is on.
>
> Please note that these are *NOT* doing streaming replication!
Could it be bug #19490 [1]?
That would be fixed in the next minor releases.
Yours,
Laurenz Albe
[1]: https://postgr.es/m/flat/19490-9c59c6a583513b99%40postgresql.org
view thread (5+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox