diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-12-23 20:09:01 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-12-23 20:09:01 -0500 |
commit | 01e386a325549b7755739f31308de4be8eea110d (patch) | |
tree | 7b3e0a819a05e4461fea9771c48ef9278bf40b18 | |
parent | ff402ae11b4d33e0e46c2730f63033d3631b8010 (diff) | |
download | postgresql-01e386a325549b7755739f31308de4be8eea110d.tar.gz postgresql-01e386a325549b7755739f31308de4be8eea110d.zip |
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 ...
-rw-r--r-- | src/bin/initdb/initdb.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/initdb/initdb.c b/src/bin/initdb/initdb.c index a27706fdb45..460342a3571 100644 --- a/src/bin/initdb/initdb.c +++ b/src/bin/initdb/initdb.c @@ -2130,7 +2130,7 @@ make_template0(FILE *cmdfd) /* * Finally vacuum to clean up dead rows in pg_database */ - "VACUUM FULL pg_database;\n\n", + "VACUUM pg_database;\n\n", NULL }; |