Re: BUG #3883: Autovacuum deadlock with truncate? - Mailing list pgsql-bugs

From Steven Flatt
Subject Re: BUG #3883: Autovacuum deadlock with truncate?
Date
Msg-id 357fa7590801180716m1ec73b69wdfc304a348887379@mail.gmail.com
Whole thread Raw
In response to Re: BUG #3883: Autovacuum deadlock with truncate?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #3883: Autovacuum deadlock with truncate?
List pgsql-bugs
On 1/17/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Do you still have the hung processes available?  It would be really
> useful to take a look at the buffer header that the autovac process's
> LockBufferForCleanup() is working on.  (In gdb, "f 3" then "p *bufHdr")

Well I just lost the hung processes a few minutes ago thanks to a
cleanup process... but I do still have cores from yesterday:

(gdb) p *bufHdr
$1 = {tag = {rnode = {spcNode = 1663, dbNode = 16384, relNode = 85707},
    blockNum = 0}, flags = 70, usage_count = 5, refcount = 2,
  wait_backend_pid = 35775, buf_hdr_lock = 0 '\0', buf_id = 14407,
  freeNext = -2, io_in_progress_lock = 28933, content_lock = 28934}

Let me know what other info I can provide.

Steve

pgsql-bugs by date:

Previous
From: "sharvari"
Date:
Subject: BUG #3885: cant create database
Next
From: Tom Lane
Date:
Subject: Re: BUG #3883: Autovacuum deadlock with truncate?