MIME-Version: 1.0
References: 
 <CAAGAcEe5Wq8XT5E_8DHS+-2pT2edSEpcGAx_ZpM6nRw3OtR33A@mail.gmail.com>
In-Reply-To: 
 <CAAGAcEe5Wq8XT5E_8DHS+-2pT2edSEpcGAx_ZpM6nRw3OtR33A@mail.gmail.com>
From: lakshmi sravya <lakshmisravya51999@gmail.com>
Date: Tue, 17 Dec 2024 15:52:17 +0530
Message-ID: 
 <CAAujgu6O8vqbVq749XhrVHRE8XgRbRV_bWVpw59+5nn-eWYD6w@mail.gmail.com>
Subject: Re: Dead tuple ratio for table & index
To: kamal deen <kamaldeendba@gmail.com>
Cc: pgsql-admin@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAAujgu6O8vqbVq749XhrVHRE8XgRbRV_bWVpw59%2B5nn-eWYD6w%40mail.gmail.com>
Precedence: bulk

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-pgstatt=
uple/

Regards,
Sravya.

On Sat, Dec 14, 2024 at 3:29=E2=80=AFAM kamal deen <kamaldeendba@gmail.com>=
 wrote:
>
> Hi All,
>
> Kindly share the query details  to identify the dead tuples ratio at tabl=
e & index level.
>
> We have noticed some of our partioned tables generating more WAL files du=
ring vacuumb.(around 50 to 60GB
>
> (We are in the plan to remove this manual job later since auto vacuum is =
enabled)
>
> Thanks in advance =E2=98=BA=EF=B8=8F
>
> Regards,
> SK