On Sun, Jun 20, 2010 at 2:04 PM, Greg Smith wrote:
> It's hard to run a 24x7 environment on 8.1. Much easier on 8.4, where the
> major things that regularly left people with quite bad VACUUM cleanup
> situations are all less likely to occur than on any previous version.
Here here. keeping anyt
venu madhav wrote:
The problem here is even though some records are cleared, it still
shows the original DB Size. Is there any way to find out the actual DB
Size or it would be more useful, if I can get the size of each table.
One of the queries at http://wiki.postgresql.org/wiki/Disk_Usage sh
Dave Crooke writes:
> 4. If you're trying to figure out the net size of the table, i.e. how much
> free space is inside the table files for reuse by PG, then you need the
> pg_stat_tuple function ... this is built in to PG 8.4, and a plug-in
> activated by a script for PG 8.3, don't know if it exi
Hi there
1. PG 8.1.9 is ancient ... you should upgrade.
2. The database gross size on disk is not affected by VACUUM ANALYZE ... all
this does is return space used by deleted row-versions to PG for re-use. The
only way to reduce it and thus return disk space to the OS is to do a VACUUM
FULL, or t
