Re: BUG #3883: Autovacuum deadlock with truncate?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #3883: Autovacuum deadlock with truncate?
Дата
Msg-id 9330.1200671899@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #3883: Autovacuum deadlock with truncate?  ("Steven Flatt" <steven.flatt@gmail.com>)
Ответы Re: BUG #3883: Autovacuum deadlock with truncate?  ("Steven Flatt" <steven.flatt@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: "Steven Flatt"
Дата:
Сообщение: Re: BUG #3883: Autovacuum deadlock with truncate?
Следующее
От: Michael Akinde
Дата:
Сообщение: Re: BUG #3881: lo_open leaks memory