Обсуждение: hot_standby_feedback via intermediate replica

Поиск
Список
Период
Сортировка

hot_standby_feedback via intermediate replica

От
Axel Rau
Дата:
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?

All are running 13.7

Any help appreciated,
Axel
---
PGP-Key: CDE74120  ☀  computing @ chaos claudius

Re: hot_standby_feedback via intermediate replica

От
Guillaume Lelarge
Дата:
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.

Re: hot_standby_feedback via intermediate replica

От
Axel Rau
Дата:


Am 23.06.2022 um 11:07 schrieb Guillaume Lelarge <guillaume@lelarge.info>:

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

Will try it.
Thanks, Axel
---
PGP-Key: CDE74120  ☀  computing @ chaos claudius