Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Date: 2010-03-19 08:52:04
Message-ID: 1268988724.3556.3.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-docspgsql-hackers
On Thu, 2010-03-18 at 23:27 +0900, Fujii Masao wrote:

> I agree that this is a bigger problem. Since the standby always starts
> walreceiver before replaying any WAL files in pg_xlog, walreceiver tries
> to receive the WAL files following the REDO starting point even if they
> have already been in pg_xlog. IOW, the same WAL files might be shipped
> from the primary to the standby many times. This behavior is unsmart,
> and should be addressed.

We might also have written half a file many times. The files in pg_xlog
are suspect whereas the files in the archive are not. If we have both we
should prefer the archive.

-- 
 Simon Riggs           www.2ndQuadrant.com


In response to

Responses

pgsql-docs by date

Next:From: Heikki LinnakangasDate: 2010-03-19 11:37:08
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Previous:From: Tim LandscheidtDate: 2010-03-18 15:52:31
Subject: [PATCH] Explain generate_subscripts() more clearly

pgsql-hackers by date

Next:From: Csaba NagyDate: 2010-03-19 08:59:23
Subject: Re: Getting to beta1
Previous:From: KaiGai KoheiDate: 2010-03-19 07:22:45
Subject: [BUG] SECURITY DEFINER on call handler makes daemon crash

pgsql-committers by date

Next:From: Simon RiggsDate: 2010-03-19 10:41:22
Subject: pgsql: Reset btpo.xact following recovery of btree delete page.
Previous:From: Peter EisentrautDate: 2010-03-18 20:00:51
Subject: pgsql: Also print the libpq error message when lo_create or lo_open

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group