Skip site navigation (1) Skip section navigation (2)

Re: Writing Commit Status hint bits (was Re: [HACKERS] Constant

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Writing Commit Status hint bits (was Re: [HACKERS] Constant
Date: 2005-07-22 16:22:52
Message-ID: 1122049372.21502.146.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Fri, 2005-07-22 at 09:40 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > In general, the hint bits are good. In *some* cases, not. I still seek
> > control over that as a designer.

...

> ... not be worth
> solving with a knob as klugy and potentially dangerous as
> suppress_hint_bits.

I note that heap_get_latest_tid() relies upon the setting of
HEAP_XMIN_COMMITTED in the infomask in lieu of checking any return codes
from the HeapTupleSatisfies check. Sequences also touch on that.

I agree with you that it is potentially dangerous to mess with that, for
now.

I'll look at Read-Only Tables for 8.2 rather than this quick-fix.

Best Regards, Simon Riggs



In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-07-22 16:31:59
Subject: Re: Buildfarm failure - pl/tcl on snake
Previous:From: Rocco AltierDate: 2005-07-22 16:21:08
Subject: Re: [HACKERS] regressin failure on latest CVS

pgsql-patches by date

Next:From: Patrick WelcheDate: 2005-07-22 16:49:05
Subject: Re: COPY FROM performance improvements
Previous:From: Rocco AltierDate: 2005-07-22 16:21:08
Subject: Re: [HACKERS] regressin failure on latest CVS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group