On Fri, 2005-07-22 at 09:40 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> 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
> suppres
Simon Riggs <[EMAIL PROTECTED]> writes:
> In general, the hint bits are good. In *some* cases, not. I still seek
> control over that as a designer.
> Specifically, the scenario I want to optimize is this:
> - we load a table with lots of real time measurement data, as one child
> out of a large nu
On Wed, 2005-07-20 at 13:20 -0400, Tom Lane wrote:
> > When VACUUM freezes the xid, it *does* make sense at that point to
> > update the hint bits as a performance optimization.
>
> The hint bits are not really relevant when xmin = FrozenTransactionId,
> since any examiner of the tuple would cons
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Wed, 2005-07-20 at 09:24 -0400, Tom Lane wrote:
>> We don't rely on any one write of them to work, but that doesn't mean
>> that we can indefinitely postpone writing them.
> OK, I think I understand where you're coming from now.
Apparently not :-(
> W
On Wed, 2005-07-20 at 09:24 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Tue, 2005-07-19 at 22:24 -0400, Tom Lane wrote:
> >> Simon Riggs <[EMAIL PROTECTED]> writes:
> >>> Short patch enclosed to turn off writing of commit-status hint bits.
> >>
> >> Doesn't this entire
