RE: Monitoring DB size - Mailing list pgsql-general

From Shenavai, Manuel
Subject RE: Monitoring DB size
Date
Msg-id AM9PR02MB741009D9AAE6CCC6234F800BE8A22@AM9PR02MB7410.eurprd02.prod.outlook.com
Whole thread Raw
In response to Re: Monitoring DB size  (Muhammad Imtiaz <imtiaz.m@bitnine.net>)
List pgsql-general

Hi Muhammad,

thanks for the suggestions. Going with pg_stat_user_tables view, we would also need to know the size of the tuple or at least an estimate.

 

Do we know the size of a tuple? Is there a maximum for the tupe size?

 

Best regards,

Manuel

 

From: Muhammad Imtiaz <imtiaz.m@bitnine.net>
Sent: 15 July 2024 17:26
To: Shenavai, Manuel <manuel.shenavai@sap.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Monitoring DB size

 

You don't often get email from imtiaz.m@bitnine.net. Learn why this is important

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, <manuel.shenavai@sap.com> wrote:

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 Size: 200 MB, live tuple 100MB, Dead Tuple: 20 MB, free space 80MB

 

Is this possible?

 

Best regards,

Manuel

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Dropping column from big table
Next
From: "Shenavai, Manuel"
Date:
Subject: RE: Monitoring DB size