On Mon, Jan 26, 2009 at 3:58 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Gregory Stark <st...@enterprisedb.com> writes: >> Put another way, the choice here is whether to have a half-baked delayed 8.4 >> release in 6 months or a polished on-time 8.5 release in 12 months. Either >> way >> the feature ships and on a not terribly different timeline either. > > This is pretty much exactly how I see it. *Hot standby is not ready*, > and committing it into 8.4 isn't going to magically make that better. > The earliest we are going to have a HS feature that I would trust my > data to is probably ten-twelve months off.
So can you give us an idea of what parts of the code are in need of rethinking etc? I assume you've looked at it now if you can estimate it's going to take another 10 -12 months? I ask because I've only seen Heikki doing any in depth public review, and he suggested a couple of weeks for the outstanding issues he's aware of. If there are fundamental problems which will take 10 - 12 months to resolve to our normal standards, then I do believe 8.5 would be more appropriate. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
