Re: Re: Hot Standby - ERROR: canceling statement due to conflict with recovery

From: raghu ram <raghuchennuru(at)gmail(dot)com>
To: Francois <lacouf(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: Hot Standby - ERROR: canceling statement due to conflict with recovery
Date: 2012-04-13 04:38:28
Message-ID: CALnrrJTmbtK6GzKYzwcKTc1Ne6yMjs2f9saYKc-0-c5Fbk27wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Apr 13, 2012 at 2:09 AM, Francois <lacouf(at)gmail(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message raghu ram 2012-04-13 05:03:22 Re: recommended schema diff tools?
Previous Message Michael Nolan 2012-04-13 00:07:33 Re: Searchable chess positions in a Postgress DB