From: | Radoslav Nedyalkov <rnedyalkov(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | conflict with recovery when delay is gone |
Date: | 2020-11-13 13:24:14 |
Message-ID: | CANhtRiaq+HPmgPiRKM6hHTzLp7kAqjP96o2+2QUZVMHP=qnqug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Forum,all
On a very busy master-standby setup which runs typical olap processing -
long living , massive writes statements, we're getting on the standby:
ERROR: canceling statement due to conflict with recovery
FATAL: terminating connection due to conflict with recovery
The weird thing is that cancellations happen usually after standby has
experienced
some huge delay(2h), still not at the allowed maximum(3h). Even recently
run statements
got cancelled when the delay is already at zero.
Sometimes the situation got relaxed after an hour or so.
Restarting the server instantly helps.
It is pg11.8, centos7, hugepages, shared_buffers 196G from 748G.
What phenomenon could we be facing?
Thank you,
Rado
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Wilson | 2020-11-13 14:32:34 | Issue upgrading from 9.5 to 13 with pg_upgrade: "connection to database failed: FATAL: database "template1" does not exist" |
Previous Message | Dennis Jacobfeuerborn | 2020-11-13 12:52:10 | "invalid record length" after restoring pg_basebackup |