From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: new full vacuum doesn't work |
Date: | 2010-01-08 11:43:36 |
Message-ID: | 162867791001080343x57a803a9n2232dae580070b16@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/1/8 Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>:
>
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>> I am testing vacuum changes, and I found some strange behave:
>
> Did you need "SET (fillfactor=100)" before vACUUM FULL?
no, I tested it and with FILLFACTOR 100 VACUUM FULL is successful.
Personally I thing, so this behave is bad. Or there is wrong default
fillfactor 0.
Regards
Pavel Stehule
>
> =# select * from pgstattuple('pgbench_accounts');
> -[ RECORD 1 ]------+-----------
> table_len | 1365336064
> tuple_count | 1000000
> tuple_len | 121000000
> tuple_percent | 8.86
> dead_tuple_count | 0
> dead_tuple_len | 0
> dead_tuple_percent | 0
> free_space | 1228669388
> free_percent | 89.99
>
> =# ALTER TABLE pgbench_accounts SET (fillfactor=100);
> ALTER TABLE
> =# vacuum full pgbench_accounts;
> VACUUM
> =# select * from pgstattuple('pgbench_accounts');
> -[ RECORD 1 ]------+----------
> table_len | 134299648
> tuple_count | 1000000
> tuple_len | 128000000
> tuple_percent | 95.31
> dead_tuple_count | 0
> dead_tuple_len | 0
> dead_tuple_percent | 0
> free_space | 1840616
> free_percent | 1.37
>
> Regards,
> ---
> Takahiro Itagaki
> NTT Open Source Software Center
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Takahiro Itagaki | 2010-01-08 11:47:17 | Re: new full vacuum doesn't work |
Previous Message | Takahiro Itagaki | 2010-01-08 11:36:34 | Re: new full vacuum doesn't work |