Re: VACUUM FULL during initdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: VACUUM FULL during initdb
Date: 2010-04-05 14:15:24
Message-ID: 20529.1270476924@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
> 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?

I had left it that way intentionally to make sure there was nothing
depending on catalogs retaining their original relfilenode number.
I'm not sure that speed of initdb is a particularly significant factor.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-04-05 14:35:19 Re: [SPAM]Re: Questions about 9.0 release note
Previous Message Tom Lane 2010-04-05 14:11:44 Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c