VACUUM FULL during initdb

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: pgsql-hackers(at)postgresql(dot)org
Subject: VACUUM FULL during initdb
Date: 2010-04-05 04:37:33
Message-ID: 20100405133733.96DB.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Do we still need VACUUM FULL in initdb? VACUUM FULL in 9.0 rewrites
all tables, so those operations are a little more expensive than
previous releases. Is it worth replacing them into VACUUM?

make_template0(void)
Finally vacuum to clean up dead rows in pg_database
"VACUUM FULL pg_database;\n",

vacuum_db(void)
PG_CMD_PUTS("ANALYZE;\nVACUUM FULL;\nVACUUM FREEZE;\n");

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message TAKATSUKA Haruka 2010-04-05 05:16:32 contrib check fail at pgcrypto on Windows Server 2008 64bit 9.0dev (HEAD near alpha5)
Previous Message Takahiro Itagaki 2010-04-05 04:15:49 Re: xmlconcat (was 9.0 release notes done)