public inbox for [email protected]
help / color / mirror / Atom feedMonitoring DB size
6+ messages / 4 participants
[nested] [flat]
* Monitoring DB size
@ 2024-07-15 14:42 Shenavai, Manuel <[email protected]>
2024-07-15 15:26 ` Re: Monitoring DB size Muhammad Imtiaz <[email protected]>
2024-07-15 16:59 ` Re: Monitoring DB size Torsten Förtsch <[email protected]>
0 siblings, 2 replies; 6+ messages in thread
From: Shenavai, Manuel @ 2024-07-15 14:42 UTC (permalink / raw)
To: [email protected] <[email protected]>
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Monitoring DB size
2024-07-15 14:42 Monitoring DB size Shenavai, Manuel <[email protected]>
@ 2024-07-15 15:26 ` Muhammad Imtiaz <[email protected]>
2024-07-16 11:37 ` RE: Monitoring DB size Shenavai, Manuel <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Muhammad Imtiaz @ 2024-07-15 15:26 UTC (permalink / raw)
To: Shenavai, Manuel <[email protected]>; +Cc: [email protected]
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, <[email protected]>
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
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: Monitoring DB size
2024-07-15 14:42 Monitoring DB size Shenavai, Manuel <[email protected]>
2024-07-15 15:26 ` Re: Monitoring DB size Muhammad Imtiaz <[email protected]>
@ 2024-07-16 11:37 ` Shenavai, Manuel <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: Shenavai, Manuel @ 2024-07-16 11:37 UTC (permalink / raw)
To: Muhammad Imtiaz <[email protected]>; +Cc: [email protected] <[email protected]>
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 <[email protected]>
Sent: 15 July 2024 17:26
To: Shenavai, Manuel <[email protected]>
Cc: [email protected]
Subject: Re: Monitoring DB size
You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification;
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, <[email protected]<mailto:[email protected]>> 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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Monitoring DB size
2024-07-15 14:42 Monitoring DB size Shenavai, Manuel <[email protected]>
@ 2024-07-15 16:59 ` Torsten Förtsch <[email protected]>
2024-07-16 11:38 ` RE: Monitoring DB size Shenavai, Manuel <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Torsten Förtsch @ 2024-07-15 16:59 UTC (permalink / raw)
To: Shenavai, Manuel <[email protected]>; +Cc: [email protected] <[email protected]>
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 *';
COPY 21
Time: 3.793 ms
postgres(2454884) =# select * from xx;
dir | sz
----------------------+-------
base | 26280
global | 568
pg_commit_ts | 12
pg_dynshmem | 4
pg_logical | 16
pg_multixact | 28
pg_notify | 4
pg_replslot | 4
pg_serial | 4
pg_snapshots | 4
pg_stat | 4
pg_stat_tmp | 4
pg_subtrans | 12
pg_tblspc | 4
pg_twophase | 4
PG_VERSION | 4
pg_wal | 16392
pg_xact | 12
postgresql.auto.conf | 4
postmaster.opts | 4
postmaster.pid | 4
(21 rows)
Time: 0.282 ms
On Mon, Jul 15, 2024 at 4:42 PM Shenavai, Manuel <[email protected]>
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
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: Monitoring DB size
2024-07-15 14:42 Monitoring DB size Shenavai, Manuel <[email protected]>
2024-07-15 16:59 ` Re: Monitoring DB size Torsten Förtsch <[email protected]>
@ 2024-07-16 11:38 ` Shenavai, Manuel <[email protected]>
2024-08-01 04:05 ` Re: Monitoring DB size semab tariq <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: Shenavai, Manuel @ 2024-07-16 11:38 UTC (permalink / raw)
To: Torsten Förtsch <[email protected]>; +Cc: [email protected] <[email protected]>
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 <[email protected]>
Sent: 15 July 2024 18:59
To: Shenavai, Manuel <[email protected]>
Cc: [email protected]
Subject: Re: Monitoring DB size
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 *';
COPY 21
Time: 3.793 ms
postgres(2454884) =# select * from xx;
dir | sz
----------------------+-------
base | 26280
global | 568
pg_commit_ts | 12
pg_dynshmem | 4
pg_logical | 16
pg_multixact | 28
pg_notify | 4
pg_replslot | 4
pg_serial | 4
pg_snapshots | 4
pg_stat | 4
pg_stat_tmp | 4
pg_subtrans | 12
pg_tblspc | 4
pg_twophase | 4
PG_VERSION | 4
pg_wal | 16392
pg_xact | 12
postgresql.auto.conf | 4
postmaster.opts | 4
postmaster.pid | 4
(21 rows)
Time: 0.282 ms
On Mon, Jul 15, 2024 at 4:42 PM Shenavai, Manuel <[email protected]<mailto:[email protected]>> 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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Monitoring DB size
2024-07-15 14:42 Monitoring DB size Shenavai, Manuel <[email protected]>
2024-07-15 16:59 ` Re: Monitoring DB size Torsten Förtsch <[email protected]>
2024-07-16 11:38 ` RE: Monitoring DB size Shenavai, Manuel <[email protected]>
@ 2024-08-01 04:05 ` semab tariq <[email protected]>
0 siblings, 0 replies; 6+ messages in thread
From: semab tariq @ 2024-08-01 04:05 UTC (permalink / raw)
To: Shenavai, Manuel <[email protected]>; +Cc: Torsten Förtsch <[email protected]>; [email protected] <[email protected]>
Hi Manuel
Sorry for the late reply saw this email just today. Anyways how about using
something like?
postgres=# SELECT
postgres-# pg_size_pretty(pg_database_size('postgres')) AS
database_size,
postgres-# pg_size_pretty(pg_total_relation_size('accounts')) AS
table_size,
postgres-# pg_size_pretty(tuple_len) AS live_tuple_size,
postgres-# pg_size_pretty(dead_tuple_len) AS dead_tuple_size,
postgres-# pg_size_pretty(free_space) AS free_space
postgres-# FROM
postgres-# pgstattuple('accounts');
database_size | table_size | live_tuple_size | dead_tuple_size |
free_space
---------------+------------+-----------------+-----------------+------------
8500 kB | 40 kB | 80 bytes | 80 bytes | 7988 bytes
(1 row)
Thanks and regards
Semab
On Tue, Jul 16, 2024 at 4:38 PM Shenavai, Manuel <[email protected]>
wrote:
> 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 <[email protected]>
> *Sent:* 15 July 2024 18:59
> *To:* Shenavai, Manuel <[email protected]>
> *Cc:* [email protected]
> *Subject:* Re: Monitoring DB size
>
>
>
> 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 *';
>
> COPY 21
> Time: 3.793 ms
> postgres(2454884) =# select * from xx;
> dir | sz
> ----------------------+-------
> base | 26280
> global | 568
> pg_commit_ts | 12
> pg_dynshmem | 4
> pg_logical | 16
> pg_multixact | 28
> pg_notify | 4
> pg_replslot | 4
> pg_serial | 4
> pg_snapshots | 4
> pg_stat | 4
> pg_stat_tmp | 4
> pg_subtrans | 12
> pg_tblspc | 4
> pg_twophase | 4
> PG_VERSION | 4
> pg_wal | 16392
> pg_xact | 12
> postgresql.auto.conf | 4
> postmaster.opts | 4
> postmaster.pid | 4
> (21 rows)
>
> Time: 0.282 ms
>
>
>
> On Mon, Jul 15, 2024 at 4:42 PM Shenavai, Manuel <[email protected]>
> 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
>
>
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2024-08-01 04:05 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-07-15 14:42 Monitoring DB size Shenavai, Manuel <[email protected]>
2024-07-15 15:26 ` Muhammad Imtiaz <[email protected]>
2024-07-16 11:37 ` Shenavai, Manuel <[email protected]>
2024-07-15 16:59 ` Torsten Förtsch <[email protected]>
2024-07-16 11:38 ` Shenavai, Manuel <[email protected]>
2024-08-01 04:05 ` semab tariq <[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