From 825ad8ebf9bdd1eab07bf5bedde35f349a75687e Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Fri, 29 Mar 2019 19:37:35 -0500 Subject: [PATCH v1 4/8] Add comma for readability --- doc/src/sgml/bki.sgml | 2 +- doc/src/sgml/config.sgml | 4 ++-- doc/src/sgml/indices.sgml | 2 +- doc/src/sgml/installation.sgml | 2 +- doc/src/sgml/ref/create_table.sgml | 2 +- doc/src/sgml/ref/create_table_as.sgml | 2 +- doc/src/sgml/ref/pgupgrade.sgml | 4 ++-- doc/src/sgml/ref/psql-ref.sgml | 2 +- doc/src/sgml/sources.sgml | 4 ++-- 9 files changed, 12 insertions(+), 12 deletions(-) diff --git a/doc/src/sgml/bki.sgml b/doc/src/sgml/bki.sgml index aa3d6f8..e27fa76 100644 --- a/doc/src/sgml/bki.sgml +++ b/doc/src/sgml/bki.sgml @@ -403,7 +403,7 @@ 8000—9999. This minimizes the risk of OID collisions with other patches being developed concurrently. To keep the 8000—9999 range free for development purposes, after a patch has been committed - to the master git repository its OIDs should be renumbered into + to the master git repository, its OIDs should be renumbered into available space below that range. Typically, this will be done near the end of each development cycle, moving all OIDs consumed by patches committed in that cycle at the same time. The script diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 5f6873d..72f03c0 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3433,7 +3433,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows reached. The default is pause, which means recovery will be paused. promote means the recovery process will finish and the server will start to accept connections. - Finally shutdown will stop the server after reaching the + Finally, shutdown will stop the server after reaching the recovery target. @@ -4128,7 +4128,7 @@ ANY num_sync ( , REM This clause specifies optional storage parameters for a table or index; see for more - information. For backward-compatibility the WITH + information. For backward-compatibility, the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should not contain OIDs (object identifiers), OIDS=TRUE is not supported anymore. diff --git a/doc/src/sgml/ref/create_table_as.sgml b/doc/src/sgml/ref/create_table_as.sgml index 679e8f5..ececc4a 100644 --- a/doc/src/sgml/ref/create_table_as.sgml +++ b/doc/src/sgml/ref/create_table_as.sgml @@ -127,7 +127,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI This clause specifies optional storage parameters for the new table; see for more - information. For backward-compatibility the WITH + information. For backward-compatibility, the WITH clause for a table can also include OIDS=FALSE to specify that rows of the new table should contain no OIDs (object identifiers), OIDS=TRUE is not supported anymore. diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index c896882..7fee896 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -726,7 +726,7 @@ psql --username=postgres --file=script.sql postgres pg_upgrade launches short-lived postmasters in the old and new data directories. Temporary Unix socket files for communication with these postmasters are, by default, made in the current - working directory. In some situations the path name for the current + working directory. In some situations, the path name for the current directory might be too long to be a valid socket name. In that case you can use the option to put the socket files in some directory with a shorter path name. For security, be sure that that @@ -793,7 +793,7 @@ psql --username=postgres --file=script.sql postgres - In PostgreSQL 12 and later small tables by + In PostgreSQL 12 and later, small tables by default don't have a free space map, as a space optimization. If you are upgrading a pre-12 cluster, the free space maps of small tables will likewise not be transferred to the new cluster. diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 1b5d82e..2f86885 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1053,7 +1053,7 @@ testdb=> These operations are not as efficient as the SQL COPY command with a file or program data source or destination, because all data must pass through the client/server - connection. For large amounts of data the SQL + connection. For large amounts of data, the SQL command might be preferable. diff --git a/doc/src/sgml/sources.sgml b/doc/src/sgml/sources.sgml index 79f5322..520bbae 100644 --- a/doc/src/sgml/sources.sgml +++ b/doc/src/sgml/sources.sgml @@ -100,7 +100,7 @@ less -x4 There are two required elements for every message: a severity level (ranging from DEBUG to PANIC) and a primary - message text. In addition there are optional elements, the most + message text. In addition, there are optional elements, the most common of which is an error identifier code that follows the SQL spec's SQLSTATE conventions. ereport itself is just a shell function that exists @@ -473,7 +473,7 @@ Hint: the addendum Rationale: Messages are not necessarily displayed on terminal-type - displays. In GUI displays or browsers these formatting instructions are + displays. In GUI displays or browsers, these formatting instructions are at best ignored. -- 2.1.4