Re: XMin Hot Standby Feedback patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: XMin Hot Standby Feedback patch
Date
Msg-id AANLkTin96M5GbEyTkqdgeJcDWq2EhXc_HWNmFvhzax59@mail.gmail.com
Whole thread Raw
In response to Re: XMin Hot Standby Feedback patch  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: XMin Hot Standby Feedback patch
Re: XMin Hot Standby Feedback patch
List pgsql-hackers
On Tue, Feb 15, 2011 at 11:42 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Patch attached, no docs yet, but the patch is clear.
>
> I'm looking to commit this in next 24 hours barring objections and/or
> test failures.

Looks pretty good to me, though I haven't tested it.  I like some of
the safety valves you put in there, but I don't understand this part:

+                       /*
+                        * Feedback from standby should move us
forwards, but not too far.
+                        * Avoid grabbing XidGenLock here in case of
waits, so use
+                        * a heuristic instead.
+                        */

What's XIDGenLock got to do with it?

On another disk, I think that those warning messages are a bad idea.
That could fill up someone's disk really quickly.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: CommitFest 2011-01 as of 2011-02-04
Next
From: Robert Haas
Date:
Subject: Re: extensions and psql