Subject: Re: Updating FSM on recovery
From: Simon Riggs <simon@2ndQuadrant.com>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
In-Reply-To: <1225360678.3971.362.camel@ebony.2ndQuadrant>
References: <49072021.7010801@enterprisedb.com>
	<24334.1225205478@sss.pgh.pa.us> <49074779.2080309@enterprisedb.com>
	<9672.1225215390@sss.pgh.pa.us> <49085327.5010608@enterprisedb.com>
	<11303.1225283814@sss.pgh.pa.us>  <490972E5.1010605@enterprisedb.com>
	<1225360678.3971.362.camel@ebony.2ndQuadrant>
Content-Type: text/plain
Date: Thu, 30 Oct 2008 10:04:57 +0000
Message-Id: <1225361097.3971.367.camel@ebony.2ndQuadrant>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


On Thu, 2008-10-30 at 09:57 +0000, Simon Riggs wrote:
> On Thu, 2008-10-30 at 10:40 +0200, Heikki Linnakangas wrote:
> 
> > So, attached is a patch using an enum. Barring objections, I'll commit
> > this.
> 
> I probably agree with the changes from reading your post, but I'd ask
> that you hang fire on committing this for a few days.

Best thing from here is for me to just freeze my tree for next few days.
It will make my submission a few days out of date, but we can fix that
up fairly quickly.

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