MIME-Version: 1.0
References: 
 <CAAGAcEe5Wq8XT5E_8DHS+-2pT2edSEpcGAx_ZpM6nRw3OtR33A@mail.gmail.com>
 <CAAujgu6O8vqbVq749XhrVHRE8XgRbRV_bWVpw59+5nn-eWYD6w@mail.gmail.com>
In-Reply-To: 
 <CAAujgu6O8vqbVq749XhrVHRE8XgRbRV_bWVpw59+5nn-eWYD6w@mail.gmail.com>
From: kamal deen <kamaldeendba@gmail.com>
Date: Tue, 17 Dec 2024 16:21:53 +0530
Message-ID: 
 <CAAGAcEcbzFiNbYw9+m3xTy5mud=rXGzeZuEQwxWUufsEHrtdNg@mail.gmail.com>
Subject: Re: Dead tuple ratio for table & index
To: lakshmi sravya <lakshmisravya51999@gmail.com>
Cc: pgsql-admin@postgresql.org
Content-Type: multipart/alternative; boundary="00000000000067122c0629751692"
Archived-At: 
 <https://www.postgresql.org/message-id/CAAGAcEcbzFiNbYw9%2Bm3xTy5mud%3DrXGzeZuEQwxWUufsEHrtdNg%40mail.gmail.com>
Precedence: bulk

--00000000000067122c0629751692
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you Sravya.

SK

On Tue, Dec 17, 2024, 3:52=E2=80=AFPM lakshmi sravya <lakshmisravya51999@gm=
ail.com>
wrote:

> 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-pgsta=
ttuple/
>
> Regards,
> Sravya.
>
> On Sat, Dec 14, 2024 at 3:29=E2=80=AFAM kamal deen <kamaldeendba@gmail.co=
m> 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 i=
s
> enabled)
> >
> > Thanks in advance =E2=98=BA=EF=B8=8F
> >
> > Regards,
> > SK
>

--00000000000067122c0629751692
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Thank you Sravya.<div dir=3D"auto"><br></div><div dir=3D"=
auto">SK</div></div><br><div class=3D"gmail_quote gmail_quote_container"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Tue, Dec 17, 2024, 3:52=E2=80=AFPM l=
akshmi sravya &lt;<a href=3D"mailto:lakshmisravya51999@gmail.com">lakshmisr=
avya51999@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Hello SK,<br>
<br>
you can use the pgstattuple extension, which provides exact table and<br>
index bloat statistics.<br>
<a href=3D"https://www.postgresql.org/docs/current/pgstattuple.html" rel=3D=
"noreferrer noreferrer" target=3D"_blank">https://www.postgresql.org/docs/c=
urrent/pgstattuple.html</a><br>
<a href=3D"https://www.percona.com/blog/postgresql-tuple-level-statistics-w=
ith-pgstattuple/" rel=3D"noreferrer noreferrer" target=3D"_blank">https://w=
ww.percona.com/blog/postgresql-tuple-level-statistics-with-pgstattuple/</a>=
<br>
<br>
Regards,<br>
Sravya.<br>
<br>
On Sat, Dec 14, 2024 at 3:29=E2=80=AFAM kamal deen &lt;<a href=3D"mailto:ka=
maldeendba@gmail.com" target=3D"_blank" rel=3D"noreferrer">kamaldeendba@gma=
il.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi All,<br>
&gt;<br>
&gt; Kindly share the query details=C2=A0 to identify the dead tuples ratio=
 at table &amp; index level.<br>
&gt;<br>
&gt; We have noticed some of our partioned tables generating more WAL files=
 during vacuumb.(around 50 to 60GB<br>
&gt;<br>
&gt; (We are in the plan to remove this manual job later since auto vacuum =
is enabled)<br>
&gt;<br>
&gt; Thanks in advance =E2=98=BA=EF=B8=8F<br>
&gt;<br>
&gt; Regards,<br>
&gt; SK<br>
</blockquote></div>

--00000000000067122c0629751692--