| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Don Seiler <don(at)seiler(dot)us>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: terminating connection due to conflict with recovery |
| Date: | 2020-10-09 15:06:00 |
| Message-ID: | 82d9b8f97e58718be841129026fabfd85ddb7ba2.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 2020-10-08 at 10:17 -0500, Don Seiler wrote:
> I have a PG 12.4 read replica that we're using to offload short read-only queries from the primary. However this morning (and random other days/times, it seems), I see batches of these messages in
> the replica PG log:
>
> FATAL: terminating connection due to conflict with recovery
>
> I have hot_standby_feedback enabled already, but looking further at this message, it isn't cancelling the transaction but rather terminating the connection entirely. This suggests perhaps that a
> session is sitting "idle in transaction" for 30 seconds (our max_standby_streaming_delay is at the default 30s)? Or that a group of sessions are "idle in transaction" and overlapping enough that
> recovery is blocked for 30 seconds?
What do you find in "pg_stat_database_conflicts"?
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hotmail | 2020-10-09 16:35:03 | Is there a way to correct an inaccurate n_distinct value for extended statistics in PG11? |
| Previous Message | Laurenz Albe | 2020-10-09 15:04:24 | Re: Dropping database in replica |