From: Andres Freund <andres@anarazel.de>
To: Soni M <diptatapa@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17399: Dead tuple number stats not updated on long running queries
Date: Thu, 10 Feb 2022 21:18:05 -0800
Message-ID: <611EAC77-3388-4FBF-8081-CBF88FDAB32F@anarazel.de> (raw)
In-Reply-To: <CAAMgDXkjqT5unq9KUa6wX+182z6j5jkC_48quztd=zDiZBxeEw@mail.gmail.com>
References: <17399-3dde82c18cf8e957@postgresql.org>
<20220211003252.drai4n4zsfqxfd5n@alap3.anarazel.de>
<CAAMgDXmL7mrXKDzQQN940rQBZdHUCuTU5kq99zV2Ag3SLZvoBA@mail.gmail.com>
<CAAMgDXkjqT5unq9KUa6wX+182z6j5jkC_48quztd=zDiZBxeEw@mail.gmail.com>
Hi,
On February 10, 2022 8:37:10 PM PST, Soni M <diptatapa@gmail.com> wrote:
>Sorry, accidentally send the message before finishing it.
>
>Ah yes, it is the dead tuple cannot be removed, because long running
>transactions still see them.
>Something that lead to my confusion above is pg_stat_progress_vacuum, each
>time autovacuum/manual vacuum launch during long running transaction, it
>reports that num_dead_tuples is 0, while the
>pg_stat_user_tables.n_dead_tuple still have the number of dead tuples.
>
>It is false reporting from pg_stat_progress_vacuum that lead to my
>confusion.
That just reports the number of dead tuples that it is tracking for removal. Not the number of tuples that could not yet be removed.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
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-bugs@postgresql.org
Cc: andres@anarazel.de, diptatapa@gmail.com
Subject: Re: BUG #17399: Dead tuple number stats not updated on long running queries
In-Reply-To: <611EAC77-3388-4FBF-8081-CBF88FDAB32F@anarazel.de>
References: <17399-3dde82c18cf8e957@postgresql.org> <20220211003252.drai4n4zsfqxfd5n@alap3.anarazel.de> <CAAMgDXmL7mrXKDzQQN940rQBZdHUCuTU5kq99zV2Ag3SLZvoBA@mail.gmail.com> <CAAMgDXkjqT5unq9KUa6wX+182z6j5jkC_48quztd=zDiZBxeEw@mail.gmail.com> <611EAC77-3388-4FBF-8081-CBF88FDAB32F@anarazel.de>
* 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