Hi Rohit,
In addition to this.
In addition to this.
As your application is very high write intensive that results into heavy streaming on the slave causing the slave read queries taking longer time not finishing in the specific time limits causing query cancellation.
You can consider tweaking the parameters max_standby_streaming_delay to the higher value to meet your business requirement completing the said query and also should consider tuning the query to increase its response time.
You can consider tweaking the parameters max_standby_streaming_delay to the higher value to meet your business requirement completing the said query and also should consider tuning the query to increase its response time.
On Sat, Nov 24, 2018 at 4:53 PM Shreeyansh Dba <shreeyansh2014@xxxxxxxxx> wrote:
On Sat, Nov 24, 2018 at 4:35 PM Rohit Arora <arora.leo9@xxxxxxxxx> wrote:Dear List,Please note that we are working on PostgreSQL 9.4.19.ThanksRohit AroraOn Sat, Nov 24, 2018 at 4:29 PM Rohit Arora <arora.leo9@xxxxxxxxx> wrote:Dear List,In few of our Slave PostgreSQL machines.I occasionally encounter below error.ERROR: canceling statement due to conflict with recoveryDETAIL: User was holding a relation lock for too longWhile 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 AdvanceRohit Arora