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 2e78013d0703211045r3120cd62u19bcc02552326a1b@mail.gmail.com
Whole thread Raw
In response to Re: CREATE INDEX and HOT - revised design  ("Merlin Moncure" <mmoncure@gmail.com>)
Responses Re: CREATE INDEX and HOT - revised design  ("Florian G. Pflug" <fgp@phlo.org>)
List pgsql-hackers


On 3/21/07, Merlin Moncure <mmoncure@gmail.com> wrote:
On 3/21/07, Pavan Deolasee <pavan.deolasee@gmail.com> wrote:
> It seems much simpler to me do something like this. But important
> question is whether the restriction that CREATE INDEX can not
> be run in a transaction block is acceptable ?

yikes -- this is huge, huge price to pay, IMHO.  Think about DDL that
implies index creation such as adding unique constraint to a table,
many postgresql users (including me) take advantage of that in update
systems to production databases.



I didn't understand that quite well. How does it help to run CREATE
INDEX inside a transaction ?

Thanks,
Pavan

--

EnterpriseDB     http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: CREATE INDEX and HOT - revised design
Next
From: Tom Lane
Date:
Subject: Re: Effects of GUC settings on automatic replans