Anthony Bull writes:
> About 3 hours after the Vacuum full completed, the disk space got returned
> to the OS - now Windows is reporting it has all that disk back. Must have
> been waiting for something? Anyway, great news!
Probably means that some session was holding on to an open-file pointer
On 2012-05-28, Anthony Bull wrote:
> After that, I ran a VACUUM FULL across the entire database, and it returned
> about 1GB to the operating system, which I think was from another large
> table that got cleaned out (but not recreated).
try a REINDEX
--
⚂⚃ 100% natural
--
Sent via pgsql-g
About 3 hours after the Vacuum full completed, the disk space got returned
to the OS - now Windows is reporting it has all that disk back. Must have
been waiting for something? Anyway, great news!
On Mon, May 28, 2012 at 11:23 PM, Anthony Bull wrote:
> I did not run analyze, only vacuum full -
I did not run analyze, only vacuum full - the disk usage reported by the OS
has stayed the same also - the data folder under postgres is still at over
25GB. Postgres itself also still reports db size at 25GB, but when I ask
postgres for a table breakdown by size, it reports only about 9GB of table
On Montag, 28. Mai 2012, Anthony Bull wrote:
Hi,
>This did not
> work either - postgres still reports 25GB being used by the
> database.
Did you run analyze?
Did the disk usage reported by the OS shrink?
Regards, Jens
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
Greetings,
I am having problems reclaiming an excessive amount of disk space used by a
database, running on Windows PostgreSQL v8.3 (unfortunately we are stuck
with this version at the moment).
The database had a 16GB table, that I deleted a lot of data from. After
deleting from this table, I ra
