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

Re: Clean shutdown and warm standby

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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:23:29
Message-ID: 1243621409.31613.61.camel@ebony.2ndQuadrant (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, 2009-05-28 at 18:09 -0400, Tom Lane wrote:

> What's your point? Surely the applied patch is a *necessary* component
> of any attempt to try to ensure archiving is complete at shutdown.
> I agree that it doesn't cover every risk factor, and there are some
> risk factors that cannot be covered by Postgres itself.  But isn't it
> a step in a desirable direction?

Well, in one way, yes. I certainly encourage Guillaume to submit more
patches and for everybody to review them, as has been done. I turned up
late to the party on this, I know.

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. 

The patch doesn't cause any problems though so we don't need to remove
it either.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-05-29 18:35:59
Subject: Re: information_schema.columns changes needed for OLEDB
Previous:From: Tom LaneDate: 2009-05-29 18:16:26
Subject: Re: [GENERAL] trouble with to_char('L')

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