From: | Rohit Arora <arora(dot)leo9(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | canceling statement coming in slave instance |
Date: | 2018-11-24 10:59:08 |
Message-ID: | CAMUAjH9FaYYJFkY6K5Exnb4ZA8KiPxOCqFCL9-AMTi+24ZYxdA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Rohit Arora | 2018-11-24 11:04:40 | Re: canceling statement coming in slave instance |
Previous Message | Ron | 2018-11-24 06:25:02 | Re: could not connect to server, in order to operate pgAdmin/PostgreSQL |