pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fred Habash <fmhabash@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Autovacuum Hung Due to Bufferpin
Date: Wed, 11 Jan 2023 16:07:00 -0500
Message-ID: <668742.1673471220@sss.pgh.pa.us> (raw)
In-Reply-To: <CADpeV5ybf-VHaS9k8GUaKCzbZRAMmT_iMYZOi1asFNth_LCQZQ@mail.gmail.com>
References: <CADpeV5xH6pjTO-fX8gufAXN2r_09C6WVNsDdriWpWV5tkyV-Ug@mail.gmail.com>
	<493122.1673451130@sss.pgh.pa.us>
	<CADpeV5ybf-VHaS9k8GUaKCzbZRAMmT_iMYZOi1asFNth_LCQZQ@mail.gmail.com>

Fred Habash <fmhabash@gmail.com> writes:
> According to pgstattuple, dead_tuple_count = 0. If this is the case, then
> what other explanations do we have?

Could be that old tuple(s) now require freezing.

> I mean, how can I find out what blocker
> session is holding the bufferpin to terminate it?

I don't think there's any ready way to discover that from SQL level.

			regards, tom lane





view thread (4+ messages)

Message-ID: <668742.1673471220@sss.pgh.pa.us>
Permalink:  ../668742.1673471220@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/668742.1673471220@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, fmhabash@gmail.com
  Subject: Re: Autovacuum Hung Due to Bufferpin
  In-Reply-To: <668742.1673471220@sss.pgh.pa.us>
  References: <CADpeV5xH6pjTO-fX8gufAXN2r_09C6WVNsDdriWpWV5tkyV-Ug@mail.gmail.com> <493122.1673451130@sss.pgh.pa.us> <CADpeV5ybf-VHaS9k8GUaKCzbZRAMmT_iMYZOi1asFNth_LCQZQ@mail.gmail.com> <668742.1673471220@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox