From: Benjamin Krajmalnik <kraj@servoyant.com>
To: pgsql-admin@postgresql.org
Subject: Question concerning replicated server using streaming replication used as a read-only reporting server
Date: Thu, 17 Jan 2013 10:49:32 -0700
Message-ID: <F4E6A2751A2823418A21D4A160B6898892B84F@fletch.stackdump.local> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
I have 2 servers which are using streaming replication (pg 9.0.4).
The secondary server is there primarily as a disaster recovery server,
but we are also using it for reporting, so as not to place undue load on
the primary server.
As I review the logs on the secondary server, I frequently see the
following:
2013-01-17 06:05:47 MST [local]ERROR: canceling statement due to
conflict with recovery
2013-01-17 06:05:47 MST [local]DETAIL: User query might have needed to
see row versions that must be removed.
2013-01-17 06:05:47 MST [local]STATEMENT: Select statement goes here
2013-01-17 06:05:47 MST [local]FATAL: terminating connection due to
conflict with recovery
2013-01-17 06:05:47 MST [local]DETAIL: User query might have needed to
see row versions that must be removed.
2013-01-17 06:05:47 MST [local]HINT: In a moment you should be able to
reconnect to the database and repeat your command.
Is there anything that can be done to mitigate this situation?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: kraj@servoyant.com
Subject: Re: Question concerning replicated server using streaming replication used as a read-only reporting server
In-Reply-To: <F4E6A2751A2823418A21D4A160B6898892B84F@fletch.stackdump.local>
References: <F4E6A2751A2823418A21D4A160B6898892B84F@fletch.stackdump.local>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox