pgsql: Avoid VACUUM FULL altogether in initdb. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Avoid VACUUM FULL altogether in initdb.
Date
Msg-id E1aBuOx-0006BX-UZ@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Avoid VACUUM FULL altogether in initdb.

Commit ed7b3b3811c5836a purported to remove initdb's use of VACUUM FULL,
as had been agreed to in a pghackers discussion back in Dec 2014.
But it missed this one ...

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/01e386a325549b7755739f31308de4be8eea110d

Modified Files
--------------
src/bin/initdb/initdb.c |    2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Improve handling of password reuse in src/bin/scripts programs.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix factual and grammatical errors in comments for struct _table