Re: Better name/syntax for "online" index creation - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: Better name/syntax for "online" index creation
Date
Msg-id e51f66da0607251249y14d147dcre7df8f655079aad5@mail.gmail.com
Whole thread Raw
In response to Re: Better name/syntax for "online" index creation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Better name/syntax for "online" index creation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 7/25/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Csaba Nagy <nagy@ecircle-ag.com> writes:
> >> Strictly speaking, however, it would have to be NOLOCKLY in that case. :-)
>
> > In this case CREATE INDEX CONCURRENTLY ... sounds better to me, although
> > the whole feature sounds nice any way you will finally call it ;-)
>
> That reads well to me too.  We'd need to check whether it can be parsed
> without making CONCURRENTLY a fully-reserved word, but offhand I think
> it would work because ON is already a fully-reserved word ...

Is there a chance that the locking variant will be replaced by
non-locking variant, or do we definitely want the locking
variant to stay?

Basically, this means whether the naming is temporary or permanent.

-- 
marko


pgsql-hackers by date:

Previous
From: Joachim Wieland
Date:
Subject: status of yet another timezone todo item
Next
From: "Marko Kreen"
Date:
Subject: Re: Getting current transaction id