[ADMIN] database size much bigger than tablespaces on filesystem

[Gabriele Bartolini]

Hi,

On Wed, 14 Sep 2011 04:03:45 -0700, Rob Audenaerde

Is this corruption of the database? Or are there ways to 'fix' this
oddity?

Try VACUUM ANALYSE and repeat the operation.

Thanks,
Gabriele

[Guillaume Lelarge]

I have a Postgresql 8.3 instance with tablespaces totalling on about 74G. This is fine.
But if I ask Postgresql how big my database is, I get a (unexpected) large answer: 595 GB.
This seems very strange. Disk I/O tests on the system are in the 'normal' range, but queries are slower than they used to be.
Is this corruption of the database? Or are there ways to 'fix' this oddity?
/usr/local/pgsql/data/tblspaces/du -c -h
74G total
All tablespaces are there. I check this by the \db command in pgsql
select pg_size_pretty(pg_database_size('database'))
595 GB

You should also check the space held in $PGDATA/base.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com

[Tom Lane]

Post by Guillaume Lelarge

select pg_size_pretty(pg_database_size('database'))
595 GB

You should also check the space held in $PGDATA/base.

I did. It is only 320 MB.

Bizarre. Try breaking the results down table-by-table to see if you can
find where the discrepancy is.

regards, tom lane

[Tom Lane]

select
tablename
, pg_relation_size(tablename)
, pg_size_pretty(pg_relation_size(tablename) ) as relsize
, pg_size_pretty(pg_total_relation_size(tablename) ) as disksize
, pg_total_relation_size(tablename)
from pg_tables where schemaname <> 'information_schema'
order by 2 desc
And all the tables report a 'disksize' larger than the 'relsize',
which seems natural. The biggest table (relsize) is around 5 GB.

pg_relation_size isn't going to count indexes nor toast tables, and
toast in particular could be where a lot of the space is. I'd suggest
sorting by pg_total_relation_size to see if anything jumps out at you.

Another problem with the above query is that it supposes that there are
no similarly-named tables in different schemas. If there are, you'll
get multiple reports of the size of the one that is visible in your
search path, and no reports for the others. If I were doing this,
I'd not rely on pg_tables but look at pg_class directly so I could use
the OID, something like

select relname, pg_total_relation_size(c.oid)
from pg_class c where relkind = 'r'
order by 2 desc

regards, tom lane