Re: hot_standby_feedback via intermediate replica - Mailing list pgsql-admin

From Guillaume Lelarge
Subject Re: hot_standby_feedback via intermediate replica
Date
Msg-id CAECtzeWvcbY8UyrapucJJB_XH94u-rUs=oZrXOaryj4xtt_10A@mail.gmail.com
Whole thread Raw
In response to hot_standby_feedback via intermediate replica  (Axel Rau <Axel.Rau@Chaos1.DE>)
Responses Re: hot_standby_feedback via intermediate replica  (Axel Rau <Axel.Rau@Chaos1.DE>)
List pgsql-admin
Hi,

Le jeu. 23 juin 2022 à 10:59, Axel Rau <Axel.Rau@chaos1.de> a écrit :
Hi all,

I’m getting:
- - -
pg_dump: error: Error message from server: ERROR:  canceling statement due to conflict with recovery
ClientBeforeJob: DETAIL:  User was holding a relation lock for too long
- - -
I have a 3-level streaming replication setup:
        primary -> standby1 -> standby2
standby2 is for backup only and shows above error.
Both standbys have
        hot_standby_feedback = on
Nvertheless the error happens.
Why?
How can I fix it?


Pause recovery on standby2 with pg_wal_replay_pause(), run pg_dump, and then resume recovery with pg_wal_replay_resume().


--
Guillaume.

pgsql-admin by date:

Previous
From: Axel Rau
Date:
Subject: hot_standby_feedback via intermediate replica
Next
From: Axel Rau
Date:
Subject: Re: hot_standby_feedback via intermediate replica