Zeugswetter Andreas DCP SD wrote:
> > > What bothers me about what we have now is that we have optional 
> > > keywords before and after INDEX, rather than only between 
> > 
> > Yeah, putting them both into that space seems consistent to 
> > me, and it will fix the problem of making an omitted index 
> > name look like a valid command.
> > 
> > I'm not sure I should be opening this can of worms, but do we 
> > want to use a different keyword than CONCURRENTLY to make it 
> > read better there?
> precedent syntax (Oracle, Informix) uses the keyword ONLINE at the end:
>  CREATE INDEX blabla_x0 ON blabla (a,b) ONLINE;

That was what the patch originally used, but it was changed because it
made difficult for psql to auto-complete that.

Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to