public inbox for [email protected]
help / color / mirror / Atom feedFrom: lakshmi sravya <[email protected]>
To: kamal deen <[email protected]>
Cc: [email protected]
Subject: Re: Dead tuple ratio for table & index
Date: Tue, 17 Dec 2024 15:52:17 +0530
Message-ID: <CAAujgu6O8vqbVq749XhrVHRE8XgRbRV_bWVpw59+5nn-eWYD6w@mail.gmail.com> (raw)
In-Reply-To: <CAAGAcEe5Wq8XT5E_8DHS+-2pT2edSEpcGAx_ZpM6nRw3OtR33A@mail.gmail.com>
References: <CAAGAcEe5Wq8XT5E_8DHS+-2pT2edSEpcGAx_ZpM6nRw3OtR33A@mail.gmail.com>
Hello SK,
you can use the pgstattuple extension, which provides exact table and
index bloat statistics.
https://www.postgresql.org/docs/current/pgstattuple.html
https://www.percona.com/blog/postgresql-tuple-level-statistics-with-pgstattuple/
Regards,
Sravya.
On Sat, Dec 14, 2024 at 3:29 AM kamal deen <[email protected]> wrote:
>
> Hi All,
>
> Kindly share the query details to identify the dead tuples ratio at table & index level.
>
> We have noticed some of our partioned tables generating more WAL files during vacuumb.(around 50 to 60GB
>
> (We are in the plan to remove this manual job later since auto vacuum is enabled)
>
> Thanks in advance ☺️
>
> Regards,
> SK
view thread (3+ messages) latest in thread
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 using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Dead tuple ratio for table & index
In-Reply-To: <CAAujgu6O8vqbVq749XhrVHRE8XgRbRV_bWVpw59+5nn-eWYD6w@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox