Re: CREATE INDEX and HOT - revised design
| От | Pavan Deolasee |
|---|---|
| Тема | Re: CREATE INDEX and HOT - revised design |
| Дата | |
| Msg-id | 2e78013d0703230551l6b84ae6et2d21a87071d92020@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: CREATE INDEX and HOT - revised design (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: CREATE INDEX and HOT - revised design
|
| Список | pgsql-hackers |
On 3/23/07, Florian G. Pflug <fgp@master.phlo.org> wrote:
Tuples in the HOT-chain may not share the same index keys with
respect to the new index being built (they share the same keys for
all existing indexes though). So we don't know which index key
to use while building the index.
Thanks,
Pavan
--
Why exactly can't a SERIALIZABLE transaction use the index it created
itself? If you add a pointer to the root of all HOT update chains where
either the HEAD is alive, or some tuple is visible to the transaction
creating the index, shouldn't this be sufficient for using the index
in the creating transaction?
Tuples in the HOT-chain may not share the same index keys with
respect to the new index being built (they share the same keys for
all existing indexes though). So we don't know which index key
to use while building the index.
Thanks,
Pavan
EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: