Re: HOT patch - version 15

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: HOT patch - version 15
Date: 2007-09-05 19:32:00
Message-ID: 21638.1189020720@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I am thinking we are best just doing the index chain we already have to
> read.

> If you are modifying the table (like with UPDATE) it makes sense to be
> more aggressive and do the whole page because you know there are
> probably other table modifications, but for an index lookup there isn't
> any knowledge of whether the table is being modified so looking at more
> than we need seems like overkill.

Uh, why would any of this code at all execute during a pure lookup?

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Robert Treat 2007-09-05 21:27:31 Re: Lazy xid assignment V4
Previous Message Andrew Dunstan 2007-09-05 19:09:21 Re: [HACKERS] pg_regress config