Re: AW: Adding index flag showing tuple status

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AW: Adding index flag showing tuple status
Date: 2001-05-18 14:59:37
Message-ID: 200105181459.f4IExbC18875@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[ Charset ISO-8859-1 unsupported, converting... ]
>
> > 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.

I wasn't going to delete it, just add a flag to index scans know they
don't need to look at the heap table.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= 2001-05-18 15:08:21 Re: Need Postgresql ODBC Driver
Previous Message Tom Lane 2001-05-18 14:45:19 Re: Queries across multiple databases (was: SELECT from a table in another database).