Re: Great change (size of data dir) upgrading postgresql

On Sun, 18 Jan 2004, Nigel J. Andrews wrote:
> > I have a vacuum command each day on my crontab :-?
>
> Is that a vacuum full? It may make a difference if the free space map hasn't
> been able to track all the deletions so that new data could reuse that
> space. The vacuum full does what could be described as data compaction. it
> moves tuples aroud to fill holes in the tuple store.

/usr/local/pgsql/bin/vacuumdb -U biologia --analyze biologia

> The other thing is the reindex. Btree indexes were well known for
> increasing in size as new records were added if those records were
> expanding the range of keys covered by an index. For example indexing
> a serial where older values were deleted and not reused didn't free
> the space in the index until 7.4. Check that out by picking a much
> updated table with an index on a field with values obtained from a
> sequence, drop that index then recreate it. Hopefully you would see a
> noteworthy decrease in disk usage.

I've not reindexed my databases.

> Of course you could look at the files within the data/base directory
> tree and see which of those are consuming alot of disk space. These
> files are named after the oid, in pg_class, of the entity they
> contain.

Where can I find this info?
data.old:
652M    351253
727M    351342
88M     351513
102M    351540

in data there is no dirs so big.

    Thank you very much for your help,
        Carlos.


       [ http://www.biologia.org/ :: portal especializado en Biología ]
 _______Carlos Costa Portela_________________________________________________
| e-mail:  ccosta@servidores.net | home page: http://casa.ccp.servidores.net |
|_____Tódalas persoas maiores foron nenos antes, pero poucas se lembran______|