Re: CREATE INDEX and HOT - revised design - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: CREATE INDEX and HOT - revised design
Date
Msg-id 200703231344.l2NDiWd21121@momjian.us
Whole thread Raw
In response to Re: CREATE INDEX and HOT - revised design  (Hannu Krosing <hannu@skype.net>)
List pgsql-hackers
Hannu Krosing wrote:
> I don't think it is a good idea to store xid's anywhere but in xmin/xmax
> columns, as doing so would cause nasty xid wraparound problems.
> 
> Instead you should wait, after completeing the index , for all
> concurrent transactions to end before you mark the index as "usable for
> queries", similar to the way CREATE INDEX CONCURRENTLY does.

We already discussed having VACUUM FREEZE deal with the pg_index xid
column.  I don't see how having CREATE INDEX wait for all completed
transactions helps us from a usability perspective.

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: CREATE INDEX and HOT - revised design
Next
From: Bruce Momjian
Date:
Subject: Re: CREATE INDEX and HOT - revised design