Re: canceling statement coming in slave instance - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: canceling statement coming in slave instance
Date
Msg-id f32941cee8bbe672bfa8ca3840795b6f8e11f24d.camel@cybertec.at
Whole thread Raw
In response to canceling statement coming in slave instance  (Rohit Arora <arora.leo9@gmail.com>)
List 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
originalvalue
 
> "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



pgsql-admin by date:

Previous
From: Ron
Date:
Subject: Re: could not connect to server, in order to operatepgAdmin/PostgreSQL
Next
From: "Lentes, Bernd"
Date:
Subject: Re: User Authentication: LDAP and "local" accounts concurrently ?