mirror of
https://github.com/postgres/postgres.git
synced 2025-07-07 00:36:50 +03:00
Fix typos and grammar in docs and comments
This fixes several areas of the documentation and some comments in matters of style, grammar, or even format. Author: Justin Pryzby Discussion: https://postgr.es/m/20201222041153.GK30237@telsasoft.com
This commit is contained in:
@ -10418,7 +10418,7 @@ get_sync_bit(int method)
|
||||
*
|
||||
* Never use O_DIRECT in walreceiver process for similar reasons; the WAL
|
||||
* written by walreceiver is normally read by the startup process soon
|
||||
* after its written. Also, walreceiver performs unaligned writes, which
|
||||
* after it's written. Also, walreceiver performs unaligned writes, which
|
||||
* don't work with O_DIRECT, so it is required for correctness too.
|
||||
*/
|
||||
if (!XLogIsNeeded() && !AmWalReceiverProcess())
|
||||
|
@ -3119,7 +3119,7 @@ get_matching_range_bounds(PartitionPruneContext *context,
|
||||
/*
|
||||
* If the smallest partition to return has MINVALUE (negative infinity) as
|
||||
* its lower bound, increment it to point to the next finite bound
|
||||
* (supposedly its upper bound), so that we don't advertently end up
|
||||
* (supposedly its upper bound), so that we don't inadvertently end up
|
||||
* scanning the default partition.
|
||||
*/
|
||||
if (minoff < boundinfo->ndatums && partindices[minoff] < 0)
|
||||
@ -3138,7 +3138,7 @@ get_matching_range_bounds(PartitionPruneContext *context,
|
||||
* If the previous greatest partition has MAXVALUE (positive infinity) as
|
||||
* its upper bound (something only possible to do with multi-column range
|
||||
* partitioning), we scan switch to it as the greatest partition to
|
||||
* return. Again, so that we don't advertently end up scanning the
|
||||
* return. Again, so that we don't inadvertently end up scanning the
|
||||
* default partition.
|
||||
*/
|
||||
if (maxoff >= 1 && partindices[maxoff] < 0)
|
||||
|
Reference in New Issue
Block a user