Re: 8.3.0 Core with concurrent vacuum fulls

From: "Gavin M(dot) Roy" <gmr(at)myyearbook(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 8.3.0 Core with concurrent vacuum fulls
Date: 2008-03-05 15:53:23
Message-ID: af1bce590803050753x38d98025ob14a625d27d562c3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2008-03-04 05:45:20 EST [6742]: [7-1] PANIC: deadlock detected
2008-03-04 05:45:20 EST [6742]: [8-1] DETAIL: Process 6742 waits for
AccessShareLock on relation 2619 of database 16385; blocked by process 6740.
Process 6740 waits for AccessShareLock on relation 1247 of database 16385;
blocked by process 6742.
2008-03-04 05:45:20 EST [6742]: [9-1] STATEMENT: VACUUM FULL
pg_catalog.pg_type

Sorry, been juggling too many things this morning!

On Wed, Mar 5, 2008 at 10:45 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "Gavin M. Roy" <gmr(at)myyearbook(dot)com> writes:
> > The panic may have made it if this is what you were looking for:
>
> > 2008-03-04 05:45:20 EST [6742]: [7-1] PANIC: deadlock detected
> > 2008-03-04 05:58:33 EST [8751]: [3-1] PANIC: deadlock detected
>
> That's what I expected to find, but where's the DETAIL for these?
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-03-05 15:56:17 Re: Batch update of indexes on data loading
Previous Message Tom Lane 2008-03-05 15:45:58 Re: 8.3.0 Core with concurrent vacuum fulls