Postgres Pro
Downloads
Home   >   mailing lists

Re: 8.3.0 Core with concurrent vacuum fulls - Mailing list pgsql-hackers

From Gavin M. Roy
Subject Re: 8.3.0 Core with concurrent vacuum fulls
Date
Msg-id af1bce590803050753x38d98025ob14a625d27d562c3@mail.gmail.com
Whole thread Raw
In response to Re: 8.3.0 Core with concurrent vacuum fulls  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 8.3.0 Core with concurrent vacuum fulls
List pgsql-hackers
Tree view
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@sss.pgh.pa.us> wrote:
"Gavin M. Roy" <gmr@myyearbook.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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 8.3.0 Core with concurrent vacuum fulls
Next
From: Bruce Momjian
Date:
Subject: Re: Batch update of indexes on data loading