aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlog.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2010-06-03 21:02:12 +0000
committerPeter Eisentraut <peter_e@gmx.net>2010-06-03 21:02:12 +0000
commitcb6038c168cac4fea81175787f3a928cddb7a42e (patch)
treedf22a40d619658cdbce11023b65c20e78ff03560 /src/backend/access/transam/xlog.c
parent667440162cc20ac7d8f67cb8830d10eeeeeb8ff7 (diff)
downloadpostgresql-cb6038c168cac4fea81175787f3a928cddb7a42e.tar.gz
postgresql-cb6038c168cac4fea81175787f3a928cddb7a42e.zip
Fix some inconsistent quoting of wal_level values in messages
When referring to postgresql.conf syntax, then it's without quotes (wal_level=archive); in narrative it's with double quotes. But never single quotes.
Diffstat (limited to 'src/backend/access/transam/xlog.c')
-rw-r--r--src/backend/access/transam/xlog.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index c154dae0a75..3024d1695e6 100644
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -7,7 +7,7 @@
* Portions Copyright (c) 1996-2010, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California
*
- * $PostgreSQL: pgsql/src/backend/access/transam/xlog.c,v 1.416 2010/06/03 03:19:59 rhaas Exp $
+ * $PostgreSQL: pgsql/src/backend/access/transam/xlog.c,v 1.417 2010/06/03 21:02:11 petere Exp $
*
*-------------------------------------------------------------------------
*/
@@ -5594,8 +5594,8 @@ CheckRequiredParameterValues(void)
if (InArchiveRecovery && ControlFile->wal_level == WAL_LEVEL_MINIMAL)
{
ereport(WARNING,
- (errmsg("WAL was generated with wal_level=\"minimal\", data may be missing"),
- errhint("This happens if you temporarily set wal_level=\"minimal\" without taking a new base backup.")));
+ (errmsg("WAL was generated with wal_level=minimal, data may be missing"),
+ errhint("This happens if you temporarily set wal_level=minimal without taking a new base backup.")));
}
/*
@@ -7731,9 +7731,9 @@ XLogReportParameters(void)
/*
* The change in number of backend slots doesn't need to be
* WAL-logged if archiving is not enabled, as you can't start
- * archive recovery with wal_level='minimal' anyway. We don't
+ * archive recovery with wal_level=minimal anyway. We don't
* really care about the values in pg_control either if
- * wal_level='minimal', but seems better to keep them up-to-date
+ * wal_level=minimal, but seems better to keep them up-to-date
* to avoid confusion.
*/
if (wal_level != ControlFile->wal_level || XLogIsNeeded())