From: | Jayadevan M <maymala(dot)jayadevan(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | vacuuming - doubt |
Date: | 2013-12-11 08:08:04 |
Message-ID: | CAFS1N4i2xYDmAHinX9SFukkddvm6druwZ146mVYCKc7yUJ8Ksw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
Another theory question -
PostgreSQL documentation says that -
"There are two variants of VACUUM: standard VACUUM and VACUUM FULL. VACUUM
FULL can reclaim more disk space "
I created a table, inserted 1000 records and deleted them. The size after a
vacuum and a vacuum full are given -
select pg_total_relation_size('myt');;
pg_total_relation_size
------------------------
65536
(1 row)
accounts=> vacuum myt;
VACUUM
accounts=> select pg_total_relation_size('myt');;
pg_total_relation_size
------------------------
16384
(1 row)
accounts=> vacuum full myt;
VACUUM
accounts=> select pg_total_relation_size('myt');;
pg_total_relation_size
------------------------
0
(1 row)
So what was the 65536 bytes left behind after standard vacuum?
Regards,
Jayadevan
From | Date | Subject | |
---|---|---|---|
Next Message | Yuriy Rusinov | 2013-12-11 08:46:24 | Re: Return setof values from C-function |
Previous Message | John R Pierce | 2013-12-11 06:40:31 | Re: Case sensitivity |