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

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Thom Brown <thom(at)linux(dot)com>
Cc: pgsql-general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ?
Date: 2026-06-18 13:33:56
Message-ID: ajPzxBmUaxQ9Ip4O@depesz.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message SolutionVetting 2026-06-18 22:29:26 Idaho state government is vetting your solution
Previous Message Thom Brown 2026-06-18 13:07:36 Re: Why is WAL-file based replica stuck for long time (hour?) in IPC:RecoveryConflictSnapshot ?