On Mon, Oct 14, 2013 at 6:31 AM, Florian Nigsch wrote:
> My question is then - where does this error come from? Is is because
> Postgres allocates the same name (table1_lower_idx) twice when the index
> begins building, because at that time there's no index present with that
> name? But if one in
2013/10/14 Florian Nigsch :
> Hi all,
>
> I am not sure if this is a bug or a misuse on my part.
>
> I am creating a number of indices in parallel on a table by using xargs. To
> do that, I write all my indices in a file indices.idx, and then have the
> indices build in parallel (in this case with
On Mon, Oct 14, 2013 at 5:31 AM, Florian Nigsch wrote:
> Hi all,
>
> I am not sure if this is a bug or a misuse on my part.
>
> I am creating a number of indices in parallel on a table by using xargs. To
> do that, I write all my indices in a file indices.idx, and then have the
> indices build in
Merlin Moncure wrote:
> On Mon, Oct 14, 2013 at 5:31 AM, Florian Nigsch wrote:
>> I am creating a number of indices in parallel on a table by using xargs. To
>> do that, I write all my indices in a file indices.idx, and then have the
>> indices build in parallel (in this case with 5 concurrent
Ian Lawrence Barwick 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 indexe
2013/10/18 Kevin Grittner :
> Ian Lawrence Barwick 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 IN
