mirror of
https://github.com/postgres/postgres.git
synced 2025-09-06 13:46:51 +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:
@@ -582,7 +582,7 @@ reduce_unique_semijoins(PlannerInfo *root)
|
||||
* Could the relation possibly be proven distinct on some set of columns?
|
||||
*
|
||||
* This is effectively a pre-checking function for rel_is_distinct_for().
|
||||
* It must return TRUE if rel_is_distinct_for() could possibly return TRUE
|
||||
* It must return true if rel_is_distinct_for() could possibly return true
|
||||
* with this rel, but it should not expend a lot of cycles. The idea is
|
||||
* that callers can avoid doing possibly-expensive processing to compute
|
||||
* rel_is_distinct_for()'s argument lists if the call could not possibly
|
||||
@@ -735,7 +735,7 @@ rel_is_distinct_for(PlannerInfo *root, RelOptInfo *rel, List *clause_list)
|
||||
* on some set of output columns?
|
||||
*
|
||||
* This is effectively a pre-checking function for query_is_distinct_for().
|
||||
* It must return TRUE if query_is_distinct_for() could possibly return TRUE
|
||||
* It must return true if query_is_distinct_for() could possibly return true
|
||||
* with this query, but it should not expend a lot of cycles. The idea is
|
||||
* that callers can avoid doing possibly-expensive processing to compute
|
||||
* query_is_distinct_for()'s argument lists if the call could not possibly
|
||||
|
Reference in New Issue
Block a user