Another HOT thought: why do we need indcreatexid at all?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
Cc: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Another HOT thought: why do we need indcreatexid at all?
Date: 2007-09-13 21:46:26
Message-ID: 27662.1189719986@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

AFAICS, the whole indcreatexid and validForTxn business is a waste of
code. By the time CREATE INDEX CONCURRENTLY is ready to set indisvalid,
surely any transactions that could see the broken HOT chains are gone.
There might have been some reason for this contraption before we had
plan invalidation, but what use is it now?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2007-09-13 22:37:18 Re: Another HOT thought: why do we need indcreatexid at all?
Previous Message Josh Berkus 2007-09-13 20:02:35 Re: RETURNING and DO INSTEAD ... Intentional or not?