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

From Rohit Arora
Subject Re: canceling statement coming in slave instance
Date
Msg-id CAMUAjH_btdjCoTvOW-rkc0KpkVx3TAv1P9C8AXjGro07T8n4wQ@mail.gmail.com
Whole thread Raw
In response to canceling statement coming in slave instance  (Rohit Arora <arora.leo9@gmail.com>)
Responses Re: canceling statement coming in slave instance  (Shreeyansh Dba <shreeyansh2014@gmail.com>)
List pgsql-admin
Dear List,

Please note that we are working on PostgreSQL 9.4.19.

Thanks
Rohit Arora


On Sat, Nov 24, 2018 at 4:29 PM Rohit Arora <arora.leo9@gmail.com> wrote:
Dear List,

In few of our Slave PostgreSQL machines.

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.

Original values:
"max_standby_archive_delay=30s"
"max_standby_streaming_delay=30s"

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.

Please note that on Master node we have heavy write  operations and these Slave nodes are geographically distinct on a WAN connection.

Thanks in Advance
Rohit Arora


pgsql-admin by date:

Previous
From: Rohit Arora
Date:
Subject: canceling statement coming in slave instance
Next
From: Shreeyansh Dba
Date:
Subject: Re: canceling statement coming in slave instance