Fix some typos
Author: Daniel Gustafsson Discussion: https://postgr.es/m/C36ADFDF-D09A-4EE5-B186-CB46C3653F4C@yesql.se
This commit is contained in:
parent
ec0294fb2c
commit
788dd0b839
@ -500,7 +500,7 @@ sanity_check_relation(Relation rel)
|
||||
/*
|
||||
* Record a single corruption found in the table. The values in ctx should
|
||||
* reflect the location of the corruption, and the msg argument should contain
|
||||
* a human readable description of the corruption.
|
||||
* a human-readable description of the corruption.
|
||||
*
|
||||
* The msg argument is pfree'd by this function.
|
||||
*/
|
||||
|
@ -892,7 +892,7 @@ sepgsql_compute_create(const char *scontext,
|
||||
* tcontext: security label of the object being referenced
|
||||
* tclass: class code (SEPG_CLASS_*) of the object being referenced
|
||||
* required: a mask of required permissions (SEPG_<class>__<perm>)
|
||||
* audit_name: a human readable object name for audit logs, or NULL.
|
||||
* audit_name: a human-readable object name for audit logs, or NULL.
|
||||
* abort_on_violation: true, if error shall be raised on access violation
|
||||
*/
|
||||
bool
|
||||
|
@ -588,7 +588,7 @@ static const ObjectPropertyType ObjectProperty[] =
|
||||
true
|
||||
},
|
||||
{
|
||||
"extented statistics",
|
||||
"extended statistics",
|
||||
StatisticExtRelationId,
|
||||
StatisticExtOidIndexId,
|
||||
STATEXTOID,
|
||||
|
@ -212,7 +212,7 @@ TypeCreate(Oid newTypeOid,
|
||||
bool isImplicitArray,
|
||||
Oid arrayType,
|
||||
Oid baseType,
|
||||
const char *defaultTypeValue, /* human readable rep */
|
||||
const char *defaultTypeValue, /* human-readable rep */
|
||||
char *defaultTypeBin, /* cooked rep */
|
||||
bool passedByValue,
|
||||
char alignment,
|
||||
|
@ -1686,7 +1686,7 @@ ComputeXidHorizons(ComputeXidHorizonsResult *h)
|
||||
* loop over all PGPROCs it is cheaper to just initialize to the
|
||||
* current top-level xid any.
|
||||
*
|
||||
* Without an assigned xid we could use a horizon as agressive as
|
||||
* Without an assigned xid we could use a horizon as aggressive as
|
||||
* ReadNewTransactionid(), but we can get away with the much cheaper
|
||||
* latestCompletedXid + 1: If this backend has no xid there, by
|
||||
* definition, can't be any newer changes in the temp table than
|
||||
|
@ -80,7 +80,7 @@ foreach my $i (@$ct932)
|
||||
}
|
||||
}
|
||||
|
||||
# extract only SJIS characers
|
||||
# extract only SJIS characters
|
||||
foreach my $i (grep defined $_->{sjis}, @mapping)
|
||||
{
|
||||
my $sjis = $i->{sjis};
|
||||
|
@ -80,7 +80,7 @@ typedef GISTPageOpaqueData *GISTPageOpaque;
|
||||
* Maximum possible sizes for GiST index tuple and index key. Calculation is
|
||||
* based on assumption that GiST page should fit at least 4 tuples. In theory,
|
||||
* GiST index can be functional when page can fit 3 tuples. But that seems
|
||||
* rather inefficent, so we use a bit conservative estimate.
|
||||
* rather inefficient, so we use a bit conservative estimate.
|
||||
*
|
||||
* The maximum size of index key is true for unicolumn index. Therefore, this
|
||||
* estimation should be used to figure out which maximum size of GiST index key
|
||||
|
@ -40,8 +40,8 @@
|
||||
*
|
||||
* Note: though this is an enum, the values are used to identify message types
|
||||
* in logical replication protocol, which uses a single byte to identify a
|
||||
* message type. Hence the values should be single byte wide and preferrably
|
||||
* human readable characters.
|
||||
* message type. Hence the values should be single-byte wide and preferably
|
||||
* human-readable characters.
|
||||
*/
|
||||
typedef enum LogicalRepMsgType
|
||||
{
|
||||
|
Loading…
x
Reference in New Issue
Block a user