Re: Online index builds

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Online index builds
Date: 2006-08-01 12:18:30
Message-ID: 200608011218.k71CIUe25944@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Adrian Maier 2006-08-01 12:24:31 Re: [HACKERS] float8 regression failure (HEAD, cygwin)
Previous Message Andrew Dunstan 2006-08-01 11:54:15 Re: Online index builds