Re: Transaction Snapshots and Hot Standby - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Transaction Snapshots and Hot Standby
Date
Msg-id 200809250122.m8P1Mnj03942@momjian.us
Whole thread Raw
In response to Re: Transaction Snapshots and Hot Standby  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Transaction Snapshots and Hot Standby  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Bruce Momjian wrote:
> Simon Riggs wrote:
> > 2. Master ignores Standby's OldestXmin
> > Effects:
> > * Long running queries on standby...
> >    Have no effect on primary
> >    Can delay apply of WAL records on standby
> > * Queries on standby give consistent answers in all cases.
> 
> Just for clarification, if you set a max_slave_delay it means it is the
> maximum amount of time WAL replay can be delayed on the slave, _and_ it
> is the maximum amount of time a query/snapshot can be guaranteed to run
> without the possibility of being canceled.  My point is that these two
> concepts are linked to the same setting.

FYI, max_slave_delay does not relate to the amount of time of data loss
in the case of master failure, assuming the WAL files are stored on the
slave in some way during the delay.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: KaiGai Kohei
Date:
Subject: Re: Updates of SE-PostgreSQL 8.4devel patches
Next
From: KaiGai Kohei
Date:
Subject: Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep)