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

From Tom Lane
Subject Re: BUG #3883: Autovacuum deadlock with truncate?
Date
Msg-id 9330.1200671899@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #3883: Autovacuum deadlock with truncate?  ("Steven Flatt" <steven.flatt@gmail.com>)
Responses Re: BUG #3883: Autovacuum deadlock with truncate?
List pgsql-bugs
"Steven Flatt" <steven.flatt@gmail.com> writes:
> (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}

Hm, PIN_COUNT_WAITER flag is still set, and refcount = 2 saying there is
still someone else pinning the buffer, so nothing evidently wrong here.

Could you check PrivateRefCount[14407] in both cores?

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Steven Flatt"
Date:
Subject: Re: BUG #3883: Autovacuum deadlock with truncate?
Next
From: Michael Akinde
Date:
Subject: Re: BUG #3881: lo_open leaks memory