From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nikhil Shetty <nikhil.dba04@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Recovery conflict due to buffer pins
Date: Mon, 13 Jun 2022 14:30:44 -0400
Message-ID: <3897574.1655145044@sss.pgh.pa.us> (raw)
In-Reply-To: <CAFpL5Vxm4B2885NqXjUmZL7zpCGgL2dy=AGtOe9F31J0X+oz5Q@mail.gmail.com>
References: <CAFpL5Vxm4B2885NqXjUmZL7zpCGgL2dy=AGtOe9F31J0X+oz5Q@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, nikhil.dba04@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Recovery conflict due to buffer pins
In-Reply-To: <3897574.1655145044@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox