Re: concurrent reindex issues

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tory M Blue <tmblue(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: concurrent reindex issues
Date: 2009-10-08 20:04:55
Message-ID: dcc563d10910081304t63358acax14fb6805c94dc14b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Oct 8, 2009 at 11:55 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wouldn't be too surprised if the LOCK is coming from some Slony
> operation or other.  You might want to ask the slony hackers about it.

I've had issues like this. Shutting down the slon daemons before
running such commands would usually allow them to finish, at the cost
of replication falling behind while it runs.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Justin T Pryzby 2009-10-08 20:16:03 Re: dump time increase by 1h with new kernel
Previous Message Tom Lane 2009-10-08 17:55:18 Re: concurrent reindex issues