From 2eb4a831e5fb5d8fc17e13aea56e04af3efe27b4 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Wed, 16 Aug 2017 00:22:32 -0400 Subject: Change TRUE/FALSE to true/false The lower case spellings are C and C++ standard and are used in most parts of the PostgreSQL sources. The upper case spellings are only used in some files/modules. So standardize on the standard spellings. The APIs for ICU, Perl, and Windows define their own TRUE and FALSE, so those are left as is when using those APIs. In code comments, we use the lower-case spelling for the C concepts and keep the upper-case spelling for the SQL concepts. Reviewed-by: Michael Paquier --- src/backend/tcop/postgres.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/backend/tcop/postgres.c') diff --git a/src/backend/tcop/postgres.c b/src/backend/tcop/postgres.c index 2c7260e564b..05c5c194ec6 100644 --- a/src/backend/tcop/postgres.c +++ b/src/backend/tcop/postgres.c @@ -2122,7 +2122,7 @@ check_log_statement(List *stmt_list) * If logging is needed, the duration in msec is formatted into msec_str[], * which must be a 32-byte buffer. * - * was_logged should be TRUE if caller already logged query details (this + * was_logged should be true if caller already logged query details (this * essentially prevents 2 from being returned). */ int -- cgit v1.2.3