Re: Re: Hot Standby - ERROR: canceling statement due to conflict with recovery - Mailing list pgsql-general

From raghu ram
Subject Re: Re: Hot Standby - ERROR: canceling statement due to conflict with recovery
Date
Msg-id CALnrrJTmbtK6GzKYzwcKTc1Ne6yMjs2f9saYKc-0-c5Fbk27wg@mail.gmail.com
Whole thread Raw
In response to Re: Hot Standby - ERROR: canceling statement due to conflict with recovery  (Francois <lacouf@gmail.com>)
List pgsql-general


On Fri, Apr 13, 2012 at 2:09 AM, Francois <lacouf@gmail.com> wrote:
One solution, for backups anyway, is to pause the replication on the slave
machines with the command: pg_xlog_replay_pause() and
pg_xlog_replay_resume().  We still don't have a solution for long running
queries, mayber have a mechanism to retry them when they fail with that
specific error.


For resolving this issue,Set below parameters values equal to total execution time of long running statements in Postgresql.conf of Standby server.

max_standby_archive_delay

max_standby_streaming_delay

and then RELOAD the PostgreSQL cluster.
--

Thanks & Regards,

Raghu Ram

EnterpriseDB: http://www.enterprisedb.com

pgsql-general by date:

Previous
From: Michael Nolan
Date:
Subject: Re: Searchable chess positions in a Postgress DB
Next
From: raghu ram
Date:
Subject: Re: recommended schema diff tools?