Re: pg_database_size() and actual disk space usage - Mailing list pgsql-admin

From Raghavendra
Subject Re: pg_database_size() and actual disk space usage
Date
Msg-id CA+h6AhgGgREbgpt2bobXUzunppWRbgii2TYMSksSbeYouM9Agg@mail.gmail.com
Whole thread Raw
In response to pg_database_size() and actual disk space usage  (Alexander Fortin <alexander.fortin@gmail.com>)
Responses Re: pg_database_size() and actual disk space usage  (Alexander Fortin <alexander.fortin@gmail.com>)
List pgsql-admin

On Thu, Mar 29, 2012 at 3:06 PM, Alexander Fortin <alexander.fortin@gmail.com> wrote:
Hi folks,

I'm analyizing why our /var/lib/postgresql partition got a quick bump in
usage (from 32GB to 41GB) few days ago, even if, according to data from
monitoring software, database size kept increasing with no bump at all.

So I'm using "SELECT pg_database_size('mydb')" but I can't find much
documentation about what that "size" actually refers to. What I see is
that both the master and the replicas shows the same number (32GB), but
for both of those I see differences in the actual file system usage:

master:
41G     /var/lib/postgresql/9.1/main/base

replica:
37G     /var/lib/postgresql/9.1/main/base/

Does pg_database_size() return size occupied by indexes too? If not, the
difference could be due to index space I guess.

Thanks!

Yes, pg_database_size include indexes in the database.

Can you also tell what replication is in place ?

---
Regards,
Raghavendra
EnterpriseDB Corporation


 
--
Alexander Fortin
http://about.me/alexanderfortin/

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

pgsql-admin by date:

Previous
From: Alexander Fortin
Date:
Subject: pg_database_size() and actual disk space usage
Next
From: Alexander Fortin
Date:
Subject: Re: pg_database_size() and actual disk space usage