Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ? - Mailing list pgsql-general

From hubert depesz lubaczewski
Subject Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ?
Date
Msg-id ajPzxBmUaxQ9Ip4O@depesz.com
Whole thread
In response to Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ?  (Thom Brown <thom@linux.com>)
Responses Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ?
List pgsql-general
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!

Best regards,

depesz




pgsql-general by date:

Previous
From: Thom Brown
Date:
Subject: Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ?
Next
From: dfgpostgres
Date:
Subject: can a linux program, running on the client side, generate data to load a temp table ?