Re: Recovery conflict due to buffer pins - Mailing list pgsql-admin

From Tom Lane
Subject Re: Recovery conflict due to buffer pins
Date
Msg-id 3897574.1655145044@sss.pgh.pa.us
Whole thread Raw
In response to Recovery conflict due to buffer pins  (Nikhil Shetty <nikhil.dba04@gmail.com>)
Responses Re: Recovery conflict due to buffer pins
List pgsql-admin
Nikhil Shetty <nikhil.dba04@gmail.com> writes:
> 2022-06-12 04:30:01 UTC [3324]: [3-1]
> user=<user>,db=postgres,app=<app>,client=127.0.0.1ERROR:  canceling
> statement due to *conflict with recovery*
> 04:30:01 UTC [3324]: [4-1]
> user=<user>,db=postgres,app=<app>,client=127.0.0.1DETAIL:  User was holding
> shared buffer pin for too long.

> We have set below parameters in standby
> hot_standby_feedback = on
> max_standby_streaming_delay = 0

> How can we avoid this error on standby?

Use a larger max_standby_streaming_delay.  Setting it to zero means
precisely that conflicting queries will be canceled immediately.

            regards, tom lane



pgsql-admin by date:

Previous
From: Nikhil Shetty
Date:
Subject: Recovery conflict due to buffer pins
Next
From: Kristjan Mustkivi
Date:
Subject: Re: Pgbouncer pool_mode and application behavior