mirror of
https://github.com/postgres/postgres.git
synced 2025-10-21 02:52:47 +03:00
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 <michael.paquier@gmail.com>
This commit is contained in:
@@ -1273,11 +1273,11 @@ AddToDataDirLockFile(int target_line, const char *str)
|
||||
|
||||
/*
|
||||
* Recheck that the data directory lock file still exists with expected
|
||||
* content. Return TRUE if the lock file appears OK, FALSE if it isn't.
|
||||
* content. Return true if the lock file appears OK, false if it isn't.
|
||||
*
|
||||
* We call this periodically in the postmaster. The idea is that if the
|
||||
* lock file has been removed or replaced by another postmaster, we should
|
||||
* do a panic database shutdown. Therefore, we should return TRUE if there
|
||||
* do a panic database shutdown. Therefore, we should return true if there
|
||||
* is any doubt: we do not want to cause a panic shutdown unnecessarily.
|
||||
* Transient failures like EINTR or ENFILE should not cause us to fail.
|
||||
* (If there really is something wrong, we'll detect it on a future recheck.)
|
||||
|
Reference in New Issue
Block a user