diff --git a/doc/src/sgml/bloom.sgml b/doc/src/sgml/bloom.sgml
index b3d0665deb..396348c523 100644
--- a/doc/src/sgml/bloom.sgml
+++ b/doc/src/sgml/bloom.sgml
@@ -212,8 +212,8 @@ CREATE INDEX
An operator class for bloom indexes requires only a hash function for the
- indexed datatype and an equality operator for searching. This example
- shows the opclass definition for the text> data type:
+ indexed data type and an equality operator for searching. This example
+ shows the operator class definition for the text> data type:
diff --git a/doc/src/sgml/brin.sgml b/doc/src/sgml/brin.sgml
index d57fd52611..f51928513c 100644
--- a/doc/src/sgml/brin.sgml
+++ b/doc/src/sgml/brin.sgml
@@ -625,7 +625,7 @@ typedef struct BrinOpcInfo
- To write an operator class for a complex datatype which has values
+ To write an operator class for a complex data type which has values
included within another type, it's possible to use the inclusion support
procedures alongside the corresponding operators, as shown
in . It requires
@@ -774,16 +774,16 @@ typedef struct BrinOpcInfo
Support procedure numbers 1-10 are reserved for the BRIN internal
functions, so the SQL level functions start with number 11. Support
function number 11 is the main function required to build the index.
- It should accept two arguments with the same datatype as the opclass,
- and return the union of them. The inclusion opclass can store union
- values with different datatypes if it is defined with the
+ It should accept two arguments with the same data type as the operator class,
+ and return the union of them. The inclusion operator class can store union
+ values with different data types if it is defined with the
STORAGE> parameter. The return value of the union
- function should match the STORAGE> datatype.
+ function should match the STORAGE> data type.
Support procedure numbers 12 and 14 are provided to support
- irregularities of built-in datatypes. Procedure number 12
+ irregularities of built-in data types. Procedure number 12
is used to support network addresses from different families which
are not mergeable. Procedure number 14 is used to support
empty ranges. Procedure number 13 is an optional but
@@ -794,17 +794,17 @@ typedef struct BrinOpcInfo
- Both minmax and inclusion opclasses support cross-datatype
+ Both minmax and inclusion operator classes support cross-data-type
operators, though with these the dependencies become more complicated.
- The minmax opclass requires a full set of operators to be
- defined with both arguments having the same datatype. It allows
- additional datatypes to be supported by defining extra sets
- of operators. Inclusion opclass operator strategies are dependent
+ The minmax operator class requires a full set of operators to be
+ defined with both arguments having the same data type. It allows
+ additional data types to be supported by defining extra sets
+ of operators. Inclusion operator class operator strategies are dependent
on another operator strategy as shown in
, or the same
operator strategy as themselves. They require the dependency
- operator to be defined with the STORAGE> datatype as the
- left-hand-side argument and the other supported datatype to be the
+ operator to be defined with the STORAGE> data type as the
+ left-hand-side argument and the other supported data type to be the
right-hand-side argument of the supported operator. See
float4_minmax_ops> as an example of minmax, and
box_inclusion_ops> as an example of inclusion.
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index c9e0ec2c02..4fb3186acf 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2006,7 +2006,7 @@ include_dir 'conf.d'
Gather node. Parallel workers are taken from the
pool of processes established by
. Note that the requested
- number of workers may not actually be available at runtime. If this
+ number of workers may not actually be available at run time. If this
occurs, the plan will run with fewer workers than expected, which may
be inefficient. The default value is 2. Setting this value to 0
disables parallel query execution.
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 35f7f11dc3..b917bdd5b2 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -3782,7 +3782,7 @@ EXEC SQL GET DESCRIPTOR name VALUE num
keywords are different. A Descriptor Area can also be manually built to
provide the input parameters for a query or a cursor and
USING SQL DESCRIPTOR name
- is the way to pass the input parameters into a parametrized query. The statement
+ is the way to pass the input parameters into a parameterized query. The statement
to build a named SQL Descriptor Area is below:
EXEC SQL SET DESCRIPTOR name VALUE numfield = :hostvar;
@@ -3917,7 +3917,7 @@ typedef struct sqlda_struct sqlda_t;
sqln>
- It contains the number of input parameters for a parametrized query in
+ It contains the number of input parameters for a parameterized query in
case it's passed into OPEN, DECLARE or
EXECUTE statements using the USING
keyword. In case it's used as output of SELECT,
@@ -8121,7 +8121,7 @@ if (*(int2 *)sqldata->sqlvar[i].sqlind != 0)
Type of the NULL indicator data. It's always SQLSMINT when returning data from the server.
- When the SQLDA is used for a parametrized query, the data is treated
+ When the SQLDA is used for a parameterized query, the data is treated
according to the set type.
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 71aae2f416..971e642276 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -17100,7 +17100,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
record
- Returns information about current controldata file state.
+ Returns information about current control file state.
@@ -17148,97 +17148,97 @@ SELECT collation for ('foo' COLLATE "de_DE");
- checkpoint_location
+ checkpoint_locationpg_lsn
- prior_location
+ prior_locationpg_lsn
- redo_location
+ redo_locationpg_lsn
- redo_wal_file
+ redo_wal_filetext
- timeline_id
+ timeline_idinteger
- prev_timeline_id
+ prev_timeline_idinteger
- full_page_writes
+ full_page_writesboolean
- next_xid
+ next_xidtext
- next_oid
+ next_oidoid
- next_multixact_id
+ next_multixact_idxid
- next_multi_offset
+ next_multi_offsetxid
- oldest_xid
+ oldest_xidxid
- oldest_xid_dbid
+ oldest_xid_dbidoid
- oldest_active_xid
+ oldest_active_xidxid
- oldest_multi_xid
+ oldest_multi_xidxid
- oldest_multi_dbid
+ oldest_multi_dbidoid
- oldest_commit_ts_xid
+ oldest_commit_ts_xidxid
- newest_commit_ts_xid
+ newest_commit_ts_xidxid
- checkpoint_time
+ checkpoint_timetimestamp with time zone
@@ -17264,22 +17264,22 @@ SELECT collation for ('foo' COLLATE "de_DE");
- pg_control_version
+ pg_control_versioninteger
- catalog_version_no
+ catalog_version_nointeger
- system_identifier
+ system_identifierbigint
- pg_control_last_modified
+ pg_control_last_modifiedtimestamp with time zone
@@ -17305,67 +17305,67 @@ SELECT collation for ('foo' COLLATE "de_DE");
- max_data_alignment
+ max_data_alignmentinteger
- database_block_size
+ database_block_sizeinteger
- blocks_per_segment
+ blocks_per_segmentinteger
- wal_block_size
+ wal_block_sizeinteger
- bytes_per_wal_segment
+ bytes_per_wal_segmentinteger
- max_identifier_length
+ max_identifier_lengthinteger
- max_index_columns
+ max_index_columnsinteger
- max_toast_chunk_size
+ max_toast_chunk_sizeinteger
- large_object_chunk_size
+ large_object_chunk_sizeinteger
- bigint_timestamps
+ bigint_timestampsboolean
- float4_pass_by_value
+ float4_pass_by_valueboolean
- float8_pass_by_value
+ float8_pass_by_valueboolean
- data_page_checksum_version
+ data_page_checksum_versioninteger
@@ -17391,27 +17391,27 @@ SELECT collation for ('foo' COLLATE "de_DE");
- min_recovery_end_location
+ min_recovery_end_locationpg_lsn
- min_recovery_end_timeline
+ min_recovery_end_timelineinteger
- backup_start_location
+ backup_start_locationpg_lsn
- backup_end_location
+ backup_end_locationpg_lsn
- end_of_backup_record_required
+ end_of_backup_record_requiredboolean
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 8834a42976..06f49dba5d 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1046,7 +1046,7 @@ primary_slot_name = 'node_a_slot'
servers. Waiting for confirmation increases the user's confidence that the
changes will not be lost in the event of server crashes but it also
necessarily increases the response time for the requesting transaction.
- The minimum wait time is the roundtrip time between primary to standby.
+ The minimum wait time is the round-trip time between primary to standby.
diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index 49d3286400..46f8e55ca9 100644
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -1315,7 +1315,7 @@ SELECT target FROM tests WHERE subject = 'some-subject' AND success;
But there's a problem: the WHERE> clause refers
to success> which is not available as a result column of the
index. Nonetheless, an index-only scan is possible because the plan does
- not need to recheck that part of the WHERE> clause at runtime:
+ not need to recheck that part of the WHERE> clause at run time:
all entries found in the index necessarily have success = true>
so this need not be explicitly checked in the
plan. PostgreSQL> versions 9.6 and later will recognize
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 6285dd05dd..f22e3da047 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -7345,7 +7345,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
In verify-full> mode, the host name is matched against the
certificate's Subject Alternative Name attribute(s), or against the
- Common Name attribute if no Subject Alternative Name of type dNSName is
+ Common Name attribute if no Subject Alternative Name of type dNSName is
present. If the certificate's name attribute starts with an asterisk
(*>), the asterisk will be treated as
a wildcard, which will match all characters except> a dot
@@ -7505,7 +7505,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
All SSL> options carry overhead in the form of encryption and
- key-exchange, so there is a tradeoff that has to be made between performance
+ key-exchange, so there is a trade-off that has to be made between performance
and security.
illustrates the risks the different sslmode> values
protect against, and what statement they make about security and overhead.
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index b620febd06..1c283a0623 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -870,7 +870,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
BtreeVacuumLock>Waiting to read or update vacuum-related information for a
- Btree index.
+ B-tree index.
AddinShmemInitLock>
diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml
index f3afedb040..bc37285066 100644
--- a/doc/src/sgml/ref/pgbench.sgml
+++ b/doc/src/sgml/ref/pgbench.sgml
@@ -266,13 +266,13 @@ pgbench options> dbname>
- Add the specified builtin script to the list of executed scripts.
+ Add the specified built-in script to the list of executed scripts.
An optional integer weight after @> allows to adjust the
probability of drawing the script. If not specified, it is set to 1.
- Available builtin scripts are: tpcb-like>,
+ Available built-in scripts are: tpcb-like>,
simple-update> and select-only>.
- Unambiguous prefixes of builtin names are accepted.
- With special name list>, show the list of builtin scripts
+ Unambiguous prefixes of built-in names are accepted.
+ With special name list>, show the list of built-in scripts
and exit immediately.
@@ -422,7 +422,7 @@ pgbench options> dbname>
- Run builtin simple-update script.
+ Run built-in simple-update script.
Shorthand for
@@ -702,7 +702,7 @@ pgbench options> dbname>
- The default builtin transaction script (also invoked with
@@ -543,7 +543,7 @@
2016-01-26 [cc988fbb0] Improve ResourceOwners' behavior for large numbers of ow
-->
- Improve performance of ResourceOwners with many tracked objects
+ Improve performance of resource owners with many tracked objects
(Aleksander Alekseev)
diff --git a/doc/src/sgml/sources.sgml b/doc/src/sgml/sources.sgml
index 13409a7994..eb85262727 100644
--- a/doc/src/sgml/sources.sgml
+++ b/doc/src/sgml/sources.sgml
@@ -935,10 +935,10 @@ MemoryContextSwitchTo(MemoryContext context)
Barring special arrangements code in signal handlers may only
- call async-signal safe functions (as defined in posix) and access
+ call async-signal safe functions (as defined in POSIX) and access
variables of type volatile sig_atomic_t. A few
- functions in postgres are also deemed signal safe, importantly
- SetLatch().
+ functions in postgres are also deemed signal safe, importantly
+ SetLatch().
In most cases signal handlers should do nothing more than note
@@ -957,9 +957,9 @@ handle_sighup(SIGNAL_ARGS)
errno = save_errno;
}
- errno> is safed and restored because
- SetLatch()> might change it. If that were not done
- interrupted code that's currently inspecting errno might see the wrong
+ errno> is saved and restored because
+ SetLatch()> might change it. If that were not done
+ interrupted code that's currently inspecting errno might see the wrong
value.
diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml
index 41151ef4bd..be5974a4ff 100644
--- a/doc/src/sgml/textsearch.sgml
+++ b/doc/src/sgml/textsearch.sgml
@@ -2798,7 +2798,7 @@ SELECT plainto_tsquery('supernova star');
to extract .aff> and .dic> files, change
extensions to .affix> and .dict>. For some
dictionary files it is also needed to convert characters to the UTF-8
- encoding with commands (for example, for norwegian language dictionary):
+ encoding with commands (for example, for a Norwegian language dictionary):
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff
iconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic