From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: Adding index flag showing tuple status |
Date: | 2001-05-18 06:26:43 |
Message-ID: | 11C1E6749A55D411A9670001FA6879633682D0@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I am looking at adding an index tuple flag to indicate when a
> heap tuple is expired so the index code can skip looking up the heap tuple.
>
> The problem is that I can't figure out how be sure that the heap tuple
> doesn't need to be looked at by _any_ backend. Right now, we update the
> transaction commit flags in the heap tuple to prevent a pg_log lookup,
> but that is not enough because some transactions may still see that heap
> tuple as visible.
If you are only marking those, that need not be visible anymore, can you not
simply delete that key (slot) from the index ? I know vacuum then shows a count
mismatch, but that could probably be accounted for.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | John Reid | 2001-05-18 06:28:47 | Re: possible DOMAIN implementation |
Previous Message | Tom Lane | 2001-05-18 06:26:09 | Re: operators and indices? |