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

Re: Clean shutdown and warm standby

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Clean shutdown and warm standby
Date: 2009-05-29 18:54:02
Message-ID: 603c8f070905291154w35c1e75cp3482d40ea4f33d82@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, May 29, 2009 at 2:23 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Regrettably, the patch doesn't remove the problem it was supposed to
> remove and I'm highlighting there is still risk of data loss. I suggest
> that we don't change any docs, and carefully word or even avoid any
> release note inclusion to avoid lulling people into stopping safety
> measures.

I think it's pretty clear that you and the OP are talking about two
different problems.  To quote Guillaume:

"Yes, the problem is that before this change, even with a working
replication and a clean shutdown, you still had to replicate the last
WAL file by hand."

I think that's a pretty legitimate complaint.  You seem to that this
wasn't worth fixing at this point in the development cycle, because it
was always possible to write a script to copy that last WAL file by
hand.  That's a judgment call, of course, and you are entitled to your
own opinion on the topic, but that doesn't mean that the complaint, as
defined by the person complaining, hasn't been fixed.

...Robert

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2009-05-29 18:59:39
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Previous:From: Heikki LinnakangasDate: 2009-05-29 18:46:25
Subject: Re: Clean shutdown and warm standby

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