| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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:17:31 |
| Message-ID: | 20091223031731.GI3949@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> >> Could we create an option to create index names automatically, so you'd
> >> only have to write
>
> >> CREATE INDEX ON foo (a);
>
> >> which would pick a name like foo_a_idx.
>
> Having done all the groundwork to support that nicely, I find that it
> doesn't work because of bison limitations :-(. AFAICT, the only way
> we could support this syntax would be to make ON a reserved word.
> Or at least more reserved than it is now. We used up all the wiggle
> room we had by making CONCURRENTLY non-reserved.
And here's Simon talking about making CONCURRENTLY more reserved so that
people stop creating indexes named "concurrently" ...
http://database-explorer.blogspot.com/2009/09/create-index-concurrently.html
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-23 03:24:13 | Re: creating index names automatically? |
| Previous Message | Tom Lane | 2009-12-23 03:09:13 | Re: creating index names automatically? |