| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Axel Rau <Axel(dot)Rau(at)chaos1(dot)de> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: hot_standby_feedback via intermediate replica |
| Date: | 2022-06-23 09:07:01 |
| Message-ID: | CAECtzeWvcbY8UyrapucJJB_XH94u-rUs=oZrXOaryj4xtt_10A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi,
Le jeu. 23 juin 2022 à 10:59, Axel Rau <Axel(dot)Rau(at)chaos1(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Axel Rau | 2022-06-23 09:31:09 | Re: hot_standby_feedback via intermediate replica |
| Previous Message | Axel Rau | 2022-06-23 08:59:28 | hot_standby_feedback via intermediate replica |