Thread

1. Status Report on Hot Standby

   Simon Riggs <simon@2ndquadrant.com> — 2009-01-17T00:16:42Z

   Bruce asked for 2 more weeks to get patches into shape for commit.
   
   Current patch v8e is attached here. Ready for commit? Up to you.
   
   My overall opinion is that it's in very good shape. Worth the community
   including it in this release and spending further time on it. I'm happy
   to stand by this going forwards.
   
   First, *all* known problems are recorded on Wiki:
   http://wiki.postgresql.org/wiki/Hot_Standby
   Much time has been spent looking at correctness issues in particular.
   
   All of Heikki's recommended refactorings have been completed and
   debugged. In the last week, Gianni and I have resolved more than 20
   issues/work items and we've reduced considerably the time for test
   cycles. Testing has been by code inspection, bash testing, regression
   test replay and specific feature tests. Special thanks to Gianni for
   performing such a large range of strange sounding tests and to the rest
   of the team's support in various ways.
   
   There are a number of items still required
   
   * Prepared Transactions - yes, its been on the list for a while, but
   there's nothing weird there and now everything else is solid it should
   take a couple of days to add
   
   * Conflict resolution for when people are connected as database/user and
   that database/user is dropped (recently raised) - some discussion needed
   
   * Fixing client/server state bug related to error handling while idle in
   transaction (which effects invalidation message handling also) 
   
   There are also a number of items I think we need to do, but are optional
   and can be added as separate items over next couple of weeks
   
   * Some simple performance tweaks, though works acceptably now
   
   * Improved conflict resolution using deferred cancellation. I think this
   is worth including and I have a fairly simple design.
   
   The patch could benefit further from input from other various hackers,
   what couldn't? It's time to put this in a shared repository (of some
   kind) and make further changes to it in a controlled manner.
   
   What now?
   
   -- 
    Simon Riggs           www.2ndQuadrant.com
    PostgreSQL Training, Services and Support
   

2. Re: Status Report on Hot Standby

   Robert Treat <xzilla@users.sourceforge.net> — 2009-01-20T23:08:20Z

   On Friday 16 January 2009 19:16:42 Simon Riggs wrote:
   > Bruce asked for 2 more weeks to get patches into shape for commit.
   >
   > Current patch v8e is attached here. Ready for commit? Up to you.
   >
   > My overall opinion is that it's in very good shape. Worth the community
   > including it in this release and spending further time on it. I'm happy
   > to stand by this going forwards.
   >
   
   +1
   
   > The patch could benefit further from input from other various hackers,
   > what couldn't? It's time to put this in a shared repository (of some
   > kind) and make further changes to it in a controlled manner.
   >
   
   Yep. I've now got this running on Linux and Solaris and testing so far has 
   looked good. I've also spoken to a couple other people who have built it and 
   run it, and everyone has been pretty happy. It'd certainly be nice to see 
   this get into the main source tree to make it easier for future testing. (For 
   example, one hurdle on Solaris, I had to get a different version of patch to 
   handle Simon's diff... ugh!) 
   
   -- 
   Robert Treat
   Conjecture: http://www.xzilla.net
   Consulting: http://www.omniti.com
   
   

3. Re: Status Report on Hot Standby

   Simon Riggs <simon@2ndquadrant.com> — 2009-01-20T23:39:40Z

   On Tue, 2009-01-20 at 18:08 -0500, Robert Treat wrote:
   
   > > The patch could benefit further from input from other various hackers,
   > > what couldn't? It's time to put this in a shared repository (of some
   > > kind) and make further changes to it in a controlled manner.
   > >
   > 
   > Yep. I've now got this running on Linux and Solaris and testing so far has 
   > looked good. I've also spoken to a couple other people who have built it and 
   > run it, and everyone has been pretty happy. It'd certainly be nice to see 
   > this get into the main source tree to make it easier for future testing. (For 
   > example, one hurdle on Solaris, I had to get a different version of patch to 
   > handle Simon's diff... ugh!) 
   
   There'll be a new version out soon, hopefully tomorrow, with some fancy
   new deferred conflict resolution. Timing depends on passage through
   testing.
   
   I think it will then be fermented in GIT for a while.
   
   -- 
    Simon Riggs           www.2ndQuadrant.com
    PostgreSQL Training, Services and Support
   
   
   

4. Re: Status Report on Hot Standby

   Mark Kirkwood <markir@paradise.net.nz> — 2009-01-21T07:39:47Z

   Robert Treat wrote:
   > On Friday 16 January 2009 19:16:42 Simon Riggs wrote:
   >   
   >> Bruce asked for 2 more weeks to get patches into shape for commit.
   >>
   >> Current patch v8e is attached here. Ready for commit? Up to you.
   >>
   >> My overall opinion is that it's in very good shape. Worth the community
   >> including it in this release and spending further time on it. I'm happy
   >> to stand by this going forwards.
   >>
   >>     
   >
   > +1
   >
   >   
   +1
   
   I've been testing several versions of this patch, and overall it looks 
   very good.
   
   regards
   
   Mark