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

From Tom Lane
Subject Re: CREATE INDEX and HOT - revised design
Date
Msg-id 19919.1175269764@sss.pgh.pa.us
Whole thread Raw
In response to Re: CREATE INDEX and HOT - revised design  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
Responses Re: CREATE INDEX and HOT - revised design  ("Pavan Deolasee" <pavan.deolasee@enterprisedb.com>)
Re: CREATE INDEX and HOT - revised design  ("Florian G. Pflug" <fgp@phlo.org>)
List pgsql-hackers
"Pavan Deolasee" <pavan.deolasee@gmail.com> writes:
> How about storing the snapshot which we used during planning in
> CachedPlanSource, if at least one index was seen unusable because
> its CREATE INDEX transaction was seen as in-progress ?

I'm getting tired of repeating this, but: the planner doesn't use a
snapshot.  System catalogs run on SnapshotNow.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Autovacuum vs statement_timeout
Next
From: "Pavan Deolasee"
Date:
Subject: Re: CREATE INDEX and HOT - revised design