suggestion. I think this will not help us to differentiate
> between live tuples, dead tuples and free space.
>
>
>
> Best regards,
>
> Manuel
>
>
>
> *From:* Torsten Förtsch
> *Sent:* 15 July 2024 18:59
> *To:* Shenavai, Manuel
> *Cc:* pgsql-genera
Thanks for the suggestion. I think this will not help us to differentiate
between live tuples, dead tuples and free space.
Best regards,
Manuel
From: Torsten Förtsch
Sent: 15 July 2024 18:59
To: Shenavai, Manuel
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Monitoring DB size
Slightly
: Shenavai, Manuel
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Monitoring DB size
You don't often get email from
imtia...@bitnine.net<mailto:imtia...@bitnine.net>. Learn why this is
important<https://aka.ms/LearnAboutSenderIdentification>
Hi,
You can choose from the
Slightly different approach than you might expect. For larger DBs you'd
likely want to exclude base and instead use pg_database_size() in addition.
postgres(2454884) =# create temp table xx(dir text, sz bigint);
CREATE TABLE
Time: 2.587 ms
postgres(2454884) =# copy xx(sz, dir) from program 'du -s
Hi,
You can choose from the following options. Hopefully, they will meet your
requirements
1) pg_stat_user_tables view
2) pgstattuple extension
Regards,
Muhammad imtiaz
On Mon, 15 Jul 2024, 19:42 Shenavai, Manuel,
wrote:
> Hi everyone,
>
>
>
> we currently capture the db size (pg_database_si
Hi everyone,
we currently capture the db size (pg_database_size) which gives the “Disk space
used by the database with the specified name”. Is it possible to further split
this data how much space is occupied by live tuples, dead tuples and free space?
We would like to have something like:
DB S
