Re: Multiple index builds on same table - in one sweep? - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: Multiple index builds on same table - in one sweep?
Date
Msg-id BANLkTin+9nd9xJ4u11C23ENCJgiteKG-Zw@mail.gmail.com
Whole thread Raw
In response to Re: Multiple index builds on same table - in one sweep?  (Greg Smith <greg@2ndquadrant.com>)
Responses Re: Multiple index builds on same table - in one sweep?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On Mon, Apr 11, 2011 at 1:41 AM, Greg Smith <greg@2ndquadrant.com> wrote:
> Scott Marlowe wrote:
>>
>> FYI, in 8.3.13 I get this for all but one index:
>>
>> ERROR:  deadlock detected
>> DETAIL:  Process 24488 waits for ShareLock on virtual transaction
>> 64/825033; blocked by process 27505.
>> Process 27505 waits for ShareUpdateExclusiveLock on relation 297369165
>> of database 278059474; blocked by process 24488.
>>
>
> Is that trying to build them by hand?  The upthread request here is actually
> already on the TODO list at http://wiki.postgresql.org/wiki/Todo and it
> talks a bit about what works and what doesn't right now:

Yes, by hand.  It creates an entry for the index but lists but marks
it as INVALID

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Slow query postgres 8.3
Next
From: Glyn Astill
Date:
Subject: Linux: more cores = less concurrency.