Re: Performance-improvement idea: shortcircuit unique-index checks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance-improvement idea: shortcircuit unique-index checks
Date: 2001-02-19 21:21:29
Message-ID: 28437.982617689@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Seems a better solution would be to put a 'deleted' bit in the index so
> we would have to visit those heap tuples only once for a committed
> status. Similar to what we do with heap tuples so we don't have to
> visit pg_log repeatedly.

That's only a partial solution, since the index is still going to have
to visit the row's existing tuple (which is, by definition, not yet
committed dead). My point is that the index scanning done for
uniqueness checks can be eliminated *entirely* for one pretty-common
case.

A deleted bit in index entries might be useful too, but I think it
attacks a different set of cases.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2001-02-19 21:37:53 Re: PHP 4.0.4pl1 / Beta 5
Previous Message Bruce Momjian 2001-02-19 21:12:43 Re: Performance-improvement idea: shortcircuit unique-index checks