Migrating tables to new tablespace, freed up space doesn't match moved data

[Brian Fehrle]

Hi all,

I've set up a tablespace on a different partition from the main data
directory. I moved a few tables and indexes over to the new tablespace
and the disk space used in this new tablespace doesn't match the amount
of data 'freed up' from the main data directory. The tablespace is
sitting at 15 GB used, but the space freed up on the main partition is
about 10 GB.

Any thoughts as to why I didn't see as much space freed up as I thought
I would?

Thanks,
- Brian F

[Prashanth Ranjalkar]

When any files that are in large size moved out or deleted, the reclaiming
of the space at certain operating system level may not be fast enough as
soon as the operation is completed and may take time.. Another possibility
would be that stats are not updated, worth to analyze the tables that are
moved into tablespace.

**
*Thanks & Regards,*
*** *
*Prashanth Ranjalkar*
*Database Consultant & Architect*
*www.postgresdba.net*

Post by Brian Fehrle
Hi all,
I've set up a tablespace on a different partition from the main data
directory. I moved a few tables and indexes over to the new tablespace and
the disk space used in this new tablespace doesn't match the amount of data
'freed up' from the main data directory. The tablespace is sitting at 15 GB
used, but the space freed up on the main partition is about 10 GB.
Any thoughts as to why I didn't see as much space freed up as I thought I
would?
Thanks,
- Brian F
--
http://www.postgresql.org/**mailpref/pgsql-admin<http://www.postgresql.org/mailpref/pgsql-admin>