Re: double vacuum in initdb

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I think we could go to
> PG_CMD_PUTS("ANALYZE;\nVACUUM FULL FREEZE;\n");
>
> without any degradation of the intended results.
>
> Another idea would be to drop the FULL part and make this
>
> PG_CMD_PUTS("ANALYZE;\nVACUUM FREEZE;\n");

We want to finish with VACUUM FREEZE without the FULL, unless we
don't care about missing visibility maps and free space maps.

[ initdb and start the cluster ]

server started
kgrittn(at)Kevin-Desktop:~/pg/master$ find Debug/data -type f | xargs ls -l >~/ls1

kgrittn(at)Kevin-Desktop:~/pg/master$ psql -c "vacuum freeze;" postgres
VACUUM
kgrittn(at)Kevin-Desktop:~/pg/master$ find Debug/data -type f | xargs ls -l >~/ls2

kgrittn(at)Kevin-Desktop:~/pg/master$ psql -c "vacuum full freeze;" postgres
VACUUM
kgrittn(at)Kevin-Desktop:~/pg/master$ find Debug/data -type f | xargs ls -l >~/ls3
kgrittn(at)Kevin-Desktop:~/pg/master$ grep _fsm <~/ls1 | wc -l
116
kgrittn(at)Kevin-Desktop:~/pg/master$ grep _fsm <~/ls2 | wc -l
119
kgrittn(at)Kevin-Desktop:~/pg/master$ grep _fsm <~/ls3 | wc -l
80
kgrittn(at)Kevin-Desktop:~/pg/master$ grep _vm <~/ls1 | wc -l
116
kgrittn(at)Kevin-Desktop:~/pg/master$ grep _vm <~/ls2 | wc -l
117
kgrittn(at)Kevin-Desktop:~/pg/master$ grep _vm <~/ls3 | wc -l
77

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company