On Fri, Apr 1, 2011 at 11:18 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Haas wrote:
>> Oh, quite right. Sorry I missed that. I suppose if we wanted to fix
>> this for real, we'd want to get:
>> But it doesn't seem worth getting excited about.
> I think (?) the problem with that is the every time you wrap around you
> get more out of sync. :-O
It's not clear to me that it matters a bit, though.
> Thinking more, the problem is that when the xid counter wraps around
> from max_xid to 3, we jump the freeze horizon by three, e.g 5000 to
> 5003. So when, the freeze horizon wraps, we can either have that jump
> by three, e.g set it to FirstNormalTransactionId, or delay by three,
> e.g. set it to MaxTransactionId.
So what? :-)
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Merlin Moncure||Date: 2011-04-01 16:43:14|
|Subject: Re: Process local hint bit cache|
|Previous:||From: Thom Brown||Date: 2011-04-01 15:57:11|
|Subject: Re: pgsql: Support comments on FOREIGN DATA WRAPPER and