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: <490972E5.1010605@enterprisedb.com>
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>
Content-Type: text/plain
Date: Thu, 30 Oct 2008 09:57:58 +0000
Message-Id: <1225360678.3971.362.camel@ebony.2ndQuadrant>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


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.

It's just going to prevent Koichi and myself from submitting clean
patches on F-Day, or it will cause us to spend time on rework before
we've even submitted the patch. I'd like to avoid the pileup for now,
though don't have any problem with the rework after that point.

Thanks,

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