Re: Multiple index builds on same table - in one sweep?

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Multiple index builds on same table - in one sweep?
Date: 2011-04-11 07:57:35
Message-ID: BANLkTin+9nd9xJ4u11C23ENCJgiteKG-Zw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Apr 11, 2011 at 1:41 AM, Greg Smith <greg(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Glyn Astill 2011-04-11 13:04:08 Linux: more cores = less concurrency.
Previous Message Greg Smith 2011-04-11 07:41:24 Re: Multiple index builds on same table - in one sweep?