Re: VACUUM FULL during initdb - Mailing list pgsql-hackers

From Tom Lane
Subject Re: VACUUM FULL during initdb
Date
Msg-id 20529.1270476924@sss.pgh.pa.us
Whole thread Raw
In response to VACUUM FULL during initdb  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-hackers
Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c
Next
From: Peter Eisentraut
Date:
Subject: Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c