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

From Pavan Deolasee
Subject Re: CREATE INDEX and HOT - revised design
Date
Msg-id 2e78013d0703210959t5b0314cbk5d34738758c41911@mail.gmail.com
Whole thread Raw
In response to Re: CREATE INDEX and HOT - revised design  (Bruce Momjian <bruce@momjian.us>)
Responses Re: CREATE INDEX and HOT - revised design  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers


On 3/21/07, Bruce Momjian <bruce@momjian.us> wrote:


I am worried that will require CREATE INDEX to wait for a long time.


Not unless there are long running transactions. We are not waiting
for the lock, but only for the current transactions to finish.



Is the pg_index xid idea too complex?  It seems to give you the
per-tuple index bit, without the restrictions.


How do we handle HEAP_ONLY tuple cleanup ? If I understood
the proposal correctly, at the end of the create index, a HEAP_ONLY
tuple may have pointer from the new index, isn't it ?
 

Thanks,
Pavan

--

EnterpriseDB     http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: CREATE INDEX and HOT - revised design
Next
From: Bruce Momjian
Date:
Subject: Re: CREATE INDEX and HOT - revised design