Rob Audenaerde writes:
> It gets stranger. I try this:
> 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 whe
I check te database size like this:
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 discrepan
Rob Audenaerde writes:
>>> I check te database size like this:
>>> 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 wh
>On Wed, 2011-09-14 at 04:03 -0700, Rob Audenaerde wrote:
>> 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 Wed, 2011-09-14 at 04:03 -0700, Rob Audenaerde wrote:
> 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 th
Hi,
On Wed, 14 Sep 2011 04:03:45 -0700, Rob Audenaerde
wrote:
Is this corruption of the database? Or are there ways to 'fix' this
oddity?
Try VACUUM ANALYSE and repeat the operation.
Thanks,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
ga
