| From: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Florian Nigsch <flo(at)nigsch(dot)eu>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Index creation fails with automatic names |
| Date: | 2013-10-17 22:40:47 |
| Message-ID: | CAB8KJ=hSJqq1zRywW-RE2PZ-Uorf46tLcKP8o-mhTsnKd8bhBg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2013/10/18 Kevin Grittner <kgrittn(at)ymail(dot)com>:
> Ian Lawrence Barwick <barwick(at)gmail(dot)com> wrote:
>
>> It works fine for me on Pg 9.3.1:
>>
>> postgres=# CREATE TABLE foo(val1 text, val2 text);
>> CREATE TABLE
>> postgres=# CREATE INDEX on foo((lower(val1)));
>> CREATE INDEX
>> postgres=# CREATE INDEX on foo((lower(val2)));
>> CREATE INDEX
>
> You seem to be creating the indexes one at a time, all on the same
> connection. The OP's problem occurs when starting five CREATE
> INDEX statements in five different sessions all at the same time.
(reads original email again) ah yes, brain was not properly engaged.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2013-10-18 00:07:33 | Re: [ADMIN] what's the efficient/safest way to convert database character set ? |
| Previous Message | Huang, Suya | 2013-10-17 22:15:02 | Re: werid error"index row size 3040 exceeds btree maximum, 2712" occur randomly |