pgsql: Avoid VACUUM FULL altogether in initdb.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid VACUUM FULL altogether in initdb.
Date: 2015-12-24 01:09:07
Message-ID: E1aBuOx-0006BX-UZ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-12-24 15:43:18 pgsql: Fix factual and grammatical errors in comments for struct _table
Previous Message Tom Lane 2015-12-23 20:45:58 pgsql: Improve handling of password reuse in src/bin/scripts programs.