| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | pinker <pinker(at)onet(dot)eu>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: VACUUM FULL doesn't reduce table size |
| Date: | 2015-03-09 13:09:53 |
| Message-ID: | 54FD9BA1.5050807@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 03/09/2015 04:22 AM, pinker wrote:
> Yes I have. Environment I'm working on is production snapshot, so there is no
> active transactions that could block those blocks from being removed...
>
Well the below from your original post would say different:
VACUUM FULL VERBOSE output:
INFO: vacuuming "my_table"
INFO: "my_table": found 0 removable, 2989662 nonremovable row versions
in 36910 pages
DETAIL: 2989421 dead row versions cannot be removed yet.
CPU 1.10s/1.82u sec elapsed 9.46 sec.
Query returned successfully with no result in 9826 ms.
So some information is in order:
What version of Postgres are you using?
What do you mean by 'production snapshot' or more to the point how did
you get the snapshot?
What does select * from pg_stat_activity show?
>
>
>
>
> --
> View this message in context: http://postgresql.nabble.com/VACUUM-FULL-doesn-t-reduce-table-size-tp5840782p5841085.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-03-09 13:17:02 | Re: pg_conndefaults Returning empty string |
| Previous Message | John McKown | 2015-03-09 12:11:07 | Re: Creating composite keys from csv |