Re: canceling statement coming in slave instance

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Rohit Arora <arora(dot)leo9(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: canceling statement coming in slave instance
Date: 2018-11-24 19:05:18
Message-ID: f32941cee8bbe672bfa8ca3840795b6f8e11f24d.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Rohit Arora wrote:
> I occasionally encounter below error.
>
> ERROR: canceling statement due to conflict with recovery
> DETAIL: User was holding a relation lock for too long
>
> While investigating online i came to know that this issue can be handled by below configuration parameters
>
> "max_standby_archive_delay "
> "max_standby_streaming_delay"
>
> I have increased the value of both the parameters as per below.
>
> Current values:
> "max_standby_archive_delay=30s" ----> was increased it to 300s but we did not get any benefit so we rollback it to original value
> "max_standby_streaming_delay=300s"
>
> But still i occasionally encounter the mention issue.

You'd have to set max_standby_streaming_delay to -1 to avoid the
error completely. But bear in mind that it can delay replication
arbitrarily long.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Anne Marie Harm 2018-11-24 19:32:14 Re: could not connect to server, in order to operate pgAdmin/PostgreSQL
Previous Message Ron 2018-11-24 18:10:58 Re: could not connect to server, in order to operate pgAdmin/PostgreSQL