| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CREATE INDEX and HOT - revised design |
| Date: | 2007-03-30 17:21:25 |
| Message-ID: | 2e78013d0703301021r2a071299n7a40f6fb2f845c72@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/30/07, Florian G. Pflug <fgp(at)phlo(dot)org> wrote:
>
>
>
> My idea was to store a list of xid's together with the cached plan that
> are assumed to be uncommitted accoring to the IndexSnapshot. The query
> is replanned if upon execution the IndexSnapshot assumes that one of
> these xid's is committed.
>
>
Actually, if we are using Serializable Snapshot then there is no chance
to replan the query before the transaction completes and the next
transaction to start in the session must see the index and hence
we must replan. So it would be enough just to associate a transaction
id with the cached plan. If this xid is set and our transaction id is
different than that, we replan.
Thanks,
Pavan
--
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-30 17:39:05 | Re: Autovacuum vs statement_timeout |
| Previous Message | Alvaro Herrera | 2007-03-30 17:20:19 | Re: Autovacuum vs statement_timeout |