Andrew Dunstan wrote:
> Bruce Momjian wrote:
> > Consindering the syntax for this, we currently allow read access during
> > index creation, just not write access, so I think the new syntax should
> > be:
> >
> > CREATE [ UNIQUE ] INDEX name ON table
> > [ USING method ] [ [ENABLE] WRITE [ACCESS] ]
> > ( { column | ( expression ) } [ opclass ] [, ...] )
> > [ WITH ( storage_parameter = value [, ... ] ) ]
> > [ TABLESPACE tablespace ]
> > [ WHERE predicate ]
> >
> > This is clear, and adds no new keywords.
> >
> >
>
> It's not particularly clear to me. On its face this seems to me to imply
> something about how the index will be able to be used, not about how it
> is to be built.
Yea, that was always a confusion. CREATE CONCURRENT INDEX has the same
problem. We need something that talks about the build-time behavior.
How about NOWAIT?
> > CREATE [ UNIQUE ] INDEX name ON table
> > [ USING method ] [ NOWAIT ]
> > ( { column | ( expression ) } [ opclass ] [, ...] )
> > [ WITH ( storage_parameter = value [, ... ] ) ]
> > [ TABLESPACE tablespace ]
> > [ WHERE predicate ]
-- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
