| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: creating index names automatically? |
| Date: | 2009-12-23 03:52:08 |
| Message-ID: | 20091223035208.GA4511@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David E. Wheeler wrote:
> On Dec 22, 2009, at 7:31 PM, Tom Lane wrote:
>
> > Wait a minute. I must have been looking at the wrong keyword list
> > --- ON already is reserved. The problem is exactly that it can't
> > tell whether CREATE INDEX CONCURRENTLY ON ... means to default the
> > index name or to create an index named CONCURRENTLY. So really the
> > *only* way to fix this is to make CONCURRENTLY be at least
> > type_func_name_keyword.
>
> +1 if it prevents indexes from being named "CONCURRENTLY".
Yeah, if you really want to have an index named like that you can use
double quotes. Seems a sensible compromise.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-23 03:54:35 | Re: creating index names automatically? |
| Previous Message | Tom Lane | 2009-12-23 03:48:41 | Re: join ordering via Simulated Annealing |