From: Simon Riggs <simon@2ndQuadrant.com>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: [PATCHES] Infrastructure changes for recovery
Date: Tue, 07 Oct 2008 17:07:46 +0100
Message-ID: <1223395666.4747.228.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <48EB7E11.4010603@enterprisedb.com>
References: <1221745847.3913.2408.camel@ebony.2ndQuadrant>
<18549.1221746983@sss.pgh.pa.us>
<1222121161.4445.248.camel@ebony.2ndQuadrant>
<1222184541.4445.400.camel@ebony.2ndQuadrant>
<28973.1222381719@sss.pgh.pa.us>
<1222985488.4445.1625.camel@ebony.2ndQuadrant>
<48E5544B.5050103@dunslane.net>
<1223367445.4747.105.camel@ebony.2ndQuadrant>
<13866.1223388527@sss.pgh.pa.us>
<1223389637.4747.194.camel@ebony.2ndQuadrant>
<20081007143707.GA19440@alvh.no-ip.org>
<48EB7E11.4010603@enterprisedb.com>
On Tue, 2008-10-07 at 18:19 +0300, Heikki Linnakangas wrote:
> The bottom line is that hot standby is a big feature, and probably a big
> patch. No amount of version control will work around that. Finishing all
> that in a few weeks is a very ambitious goal. I wish you luck, and I
> wish I could do more to help you with that; it's a feature I'd really
> like to see in 8.4. Given how many iterations just this part of the
> patch needed, and it's still not there, the little project manager in me
> says that we really need to be seeing the complete patch or patches very
> soon, and do a first round of review well before the commit fest. The
> risk that we have to drop it as unfinished in November is very high
> otherwise.
Agreed and understood. The coding isn't the problem, its the risk of
being blindsided by a showstopper. Coding is quick when you know exactly
what you are trying to achieve.
That's one reason to strip out the bgwriter stuff. It's the postmaster
state change stuff that's most needed. Anyway, watch this space.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-patches@postgresql.org
Cc: simon@2ndQuadrant.com, heikki.linnakangas@enterprisedb.com, alvherre@commandprompt.com, tgl@sss.pgh.pa.us, andrew@dunslane.net, pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] Infrastructure changes for recovery
In-Reply-To: <1223395666.4747.228.camel@ebony.2ndQuadrant>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox