| From: | Muhammad Imtiaz <imtiaz(dot)m(at)bitnine(dot)net> |
|---|---|
| To: | "Shenavai, Manuel" <manuel(dot)shenavai(at)sap(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Monitoring DB size |
| Date: | 2024-07-15 15:26:07 |
| Message-ID: | CANwR1ORGpwejXsyvf8W-1+UoMU3XsQbdvY+asuHYkJXbgV4THw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(dot)shenavai(at)sap(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-07-15 15:37:32 | Re: How does this FK constraint error happen? |
| Previous Message | Ron Johnson | 2024-07-15 15:18:29 | Re: How does this FK constraint error happen? |