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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-07-22 16:31:59 | Re: Buildfarm failure - pl/tcl on snake |
Previous Message | Rocco Altier | 2005-07-22 16:21:08 | Re: [HACKERS] regressin failure on latest CVS |
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Welche | 2005-07-22 16:49:05 | Re: COPY FROM performance improvements |
Previous Message | Rocco Altier | 2005-07-22 16:21:08 | Re: [HACKERS] regressin failure on latest CVS |