| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
| Cc: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: CREATE INDEX and HOT - revised design |
| Date: | 2007-03-21 18:43:39 |
| Message-ID: | 1174502620.6069.43.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2007-03-21 at 13:29 -0400, Bruce Momjian wrote:
> Pavan Deolasee wrote:
> > On 3/21/07, Bruce Momjian <bruce(at)momjian(dot)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.
>
> Waiting for all transactions might take a while, no?
It would be nice if we could force CREATE INDEX to only run outside a
transaction block, but that just isn't possible if you care about
existing applications.
Any PL function running a CREATE INDEX would fail and I'm pretty sure
there's lots of them. Many of them use dynamic SQL, so you wouldn't even
be able to scan them prior to run-time to know that they would fail.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-03-21 18:55:19 | Re: CREATE INDEX and HOT - revised design |
| Previous Message | Grzegorz Jaskiewicz | 2007-03-21 18:43:20 | Re: [PATCHES] Bitmapscan changes |