Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitc02350d

Browse files
committed
FREEZE and VERBOSE options were in wrong order in the VACUUM command that
vacuumdb produces. Per report by Thom Brown.
1 parent198483a commitc02350d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎src/bin/scripts/vacuumdb.c

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
* Portions Copyright (c) 1996-2009, PostgreSQL Global Development Group
66
* Portions Copyright (c) 1994, Regents of the University of California
77
*
8-
* $PostgreSQL: pgsql/src/bin/scripts/vacuumdb.c,v 1.26 2009/04/28 02:37:09 momjian Exp $
8+
* $PostgreSQL: pgsql/src/bin/scripts/vacuumdb.c,v 1.27 2009/10/16 10:38:25 heikki Exp $
99
*
1010
*-------------------------------------------------------------------------
1111
*/
@@ -195,10 +195,10 @@ vacuum_one_database(const char *dbname, bool full, bool verbose, bool analyze,
195195
appendPQExpBuffer(&sql,"VACUUM");
196196
if (full)
197197
appendPQExpBuffer(&sql," FULL");
198-
if (verbose)
199-
appendPQExpBuffer(&sql," VERBOSE");
200198
if (freeze)
201199
appendPQExpBuffer(&sql," FREEZE");
200+
if (verbose)
201+
appendPQExpBuffer(&sql," VERBOSE");
202202
if (analyze)
203203
appendPQExpBuffer(&sql," ANALYZE");
204204
if (table)

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp