public inbox for [email protected]  

help / color / mirror / Atom feed

Dead tuple ratio for table & index
3+ messages / 2 participants
[nested] [flat]

* Dead tuple ratio for table & index
@ 2024-12-13 21:59  kamal deen <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: kamal deen @ 2024-12-13 21:59 UTC (permalink / raw)
  To: pgsql-admin

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


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Dead tuple ratio for table & index
@ 2024-12-17 10:22  lakshmi sravya <[email protected]>
  parent: kamal deen <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: lakshmi sravya @ 2024-12-17 10:22 UTC (permalink / raw)
  To: kamal deen <[email protected]>; +Cc: pgsql-admin

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





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Dead tuple ratio for table & index
@ 2024-12-17 10:51  kamal deen <[email protected]>
  parent: lakshmi sravya <[email protected]>
  0 siblings, 0 replies; 3+ messages in thread

From: kamal deen @ 2024-12-17 10:51 UTC (permalink / raw)
  To: lakshmi sravya <[email protected]>; +Cc: pgsql-admin

Thank you Sravya.

SK

On Tue, Dec 17, 2024, 3:52 PM lakshmi sravya <[email protected]>
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-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
>


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

end of thread, other threads:[~2024-12-17 10:51 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-12-13 21:59 Dead tuple ratio for table & index kamal deen <[email protected]>
2024-12-17 10:22 ` lakshmi sravya <[email protected]>
2024-12-17 10:51   ` kamal deen <[email protected]>

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