Re: Recovery conflict due to buffer pins

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Recovery conflict due to buffer pins
Date: 2022-06-13 18:30:44
Message-ID: 3897574.1655145044@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Nikhil Shetty <nikhil(dot)dba04(at)gmail(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kristjan Mustkivi 2022-06-14 05:53:04 Re: Pgbouncer pool_mode and application behavior
Previous Message Nikhil Shetty 2022-06-13 18:05:35 Recovery conflict due to buffer pins