From 122fa9f942478f8fdcfba961e01d172574369293 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Mon, 8 Apr 2019 22:27:35 +0200 Subject: [PATCH] doc: Fix whitespace Author: Julien Rouhaud --- doc/src/sgml/client-auth.sgml | 6 +++--- doc/src/sgml/config.sgml | 2 +- doc/src/sgml/ecpg.sgml | 10 +++++----- doc/src/sgml/func.sgml | 4 ++-- doc/src/sgml/high-availability.sgml | 2 +- doc/src/sgml/json.sgml | 2 +- doc/src/sgml/monitoring.sgml | 20 ++++++++++---------- doc/src/sgml/parallel.sgml | 4 ++-- doc/src/sgml/postgres-fdw.sgml | 2 +- doc/src/sgml/protocol.sgml | 2 +- doc/src/sgml/ref/pg_basebackup.sgml | 2 +- doc/src/sgml/ref/pg_rewind.sgml | 2 +- doc/src/sgml/ref/pgupgrade.sgml | 2 +- doc/src/sgml/runtime.sgml | 2 +- doc/src/sgml/spgist.sgml | 2 +- 15 files changed, 32 insertions(+), 32 deletions(-) diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index 45a3cf3defd..ffed887ab73 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -671,7 +671,7 @@ hostnogssenc database usererror fields indicate problems in the corresponding lines of the file. - + To connect to a particular database, a user must not only pass the @@ -747,9 +747,9 @@ host all all .example.com scram-sha-256 # reject all connections from 192.168.54.1 (since that entry will be # matched first), but allow GSSAPI-encrypted connections from anywhere else # on the Internet. The zero mask causes no bits of the host IP address to -# be considered, so it matches any host. Unencrypted GSSAPI connections +# be considered, so it matches any host. Unencrypted GSSAPI connections # (which "fall through" to the third line since "hostgssenc" only matches -# encrypted GSSAPI connections) are allowed, but only from 192.168.12.10. +# encrypted GSSAPI connections) are allowed, but only from 192.168.12.10. # # TYPE DATABASE USER ADDRESS METHOD host all all 192.168.54.1/32 reject diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index d2da1abe618..75f9471ff6d 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -953,7 +953,7 @@ include_dir 'conf.d' This parameter is supported only on systems that support TCP_USER_TIMEOUT; on other systems, it must be zero. In sessions connected via a Unix-domain socket, this parameter is - ignored and always reads as zero. + ignored and always reads as zero. diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index d5ee6a58e77..1bd7cf4ebd6 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -312,7 +312,7 @@ current=testdb1 (should be testdb1) - The third option is to declare a sql identifier linked to + The third option is to declare a sql identifier linked to the connection, for example: EXEC SQL AT connection-name DECLARE statement-name STATEMENT; @@ -558,7 +558,7 @@ EXEC SQL COMMIT; - + EXEC SQL SET AUTOCOMMIT TO ON @@ -6843,7 +6843,7 @@ EXEC SQL [ AT connection_name ] DEC A database connection name established by the CONNECT command. - If AT clause is omitted, an SQL statement identifier is associated with the DEFAULT connection. + If AT clause is omitted, an SQL statement identifier is associated with the DEFAULT connection. @@ -6862,10 +6862,10 @@ EXEC SQL [ AT connection_name ] DEC - Notes + Notes AT clause can be used at other dynamic SQL statements. The following table - gives the connected database when AT clause is used at DECLARE STATEMENT + gives the connected database when AT clause is used at DECLARE STATEMENT and other dynamic statements. diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 5c3724ab9e3..6211ff39279 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -17397,7 +17397,7 @@ SET search_path TO schema, sc because it needs access to the predicate lock manager's shared state for a short time. - + version @@ -21225,7 +21225,7 @@ postgres=# SELECT * FROM pg_walfile_name_offset(pg_stop_backup()); Name Return Type Description - + pg_partition_tree diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 2b4dcd03c87..543691dad45 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1518,7 +1518,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' processing would request a file from the WAL archive, reporting failure if the file was unavailable. For standby processing it is normal for the next WAL file to be unavailable, so the standby must wait for - it to appear. For files ending in + it to appear. For files ending in .history there is no need to wait, and a non-zero return code must be returned. A waiting restore_command can be written as a custom script that loops after polling for the existence of diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index 3e0e92a7850..8c5df6f0bb0 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -625,7 +625,7 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu - jsonpath Type + jsonpath Type jsonpath diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 4eb43f2de95..9cc332b6ad1 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -3622,7 +3622,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, with write locks that can potentially see the table to finish. This phase is skipped when not in concurrent mode. Columns lockers_total, lockers_done - and current_locker_pid contain the progress + and current_locker_pid contain the progress information for this phase. @@ -3644,7 +3644,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, with write locks that can potentially write into the table to finish. This phase is skipped when not in concurrent mode. Columns lockers_total, lockers_done - and current_locker_pid contain the progress + and current_locker_pid contain the progress information for this phase. @@ -3682,7 +3682,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, that can potentially see the table to release their snapshots. This phase is skipped when not in concurrent mode. Columns lockers_total, lockers_done - and current_locker_pid contain the progress + and current_locker_pid contain the progress information for this phase. @@ -3693,7 +3693,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, with read locks on the table to finish, before marking the old index dead. This phase is skipped when not in concurrent mode. Columns lockers_total, lockers_done - and current_locker_pid contain the progress + and current_locker_pid contain the progress information for this phase. @@ -3704,7 +3704,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, with read locks on the table to finish, before dropping the old index. This phase is skipped when not in concurrent mode. Columns lockers_total, lockers_done - and current_locker_pid contain the progress + and current_locker_pid contain the progress information for this phase. @@ -3725,8 +3725,8 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, that will be reported and provide information about how to interpret it. Progress for VACUUM FULL commands is reported via pg_stat_progress_cluster - because both VACUUM FULL and CLUSTER - rewrite the table, while regular VACUUM only modifies it + because both VACUUM FULL and CLUSTER + rewrite the table, while regular VACUUM only modifies it in place. See . @@ -3912,7 +3912,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, Whenever CLUSTER or VACUUM FULL is running, the pg_stat_progress_cluster view will - contain a row for each backend that is currently running either command. + contain a row for each backend that is currently running either command. The tables below describe the information that will be reported and provide information about how to interpret it. @@ -4054,7 +4054,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, sorting tuples - CLUSTER is currently sorting tuples. + CLUSTER is currently sorting tuples. @@ -4072,7 +4072,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, performing final cleanup - The command is performing final cleanup. When this phase is + The command is performing final cleanup. When this phase is completed, CLUSTER or VACUUM FULL will end. diff --git a/doc/src/sgml/parallel.sgml b/doc/src/sgml/parallel.sgml index b0b03c54e5f..af5d48a5c79 100644 --- a/doc/src/sgml/parallel.sgml +++ b/doc/src/sgml/parallel.sgml @@ -102,7 +102,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; order-preserving merge. In contrast, Gather reads tuples from the workers in whatever order is convenient, destroying any sort order that may have existed. - + @@ -347,7 +347,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; workers in order to produce the final result. This is reflected in the plan as a Finalize Aggregate node. - + Because the Finalize Aggregate node runs on the leader process, queries which produce a relatively large number of groups in diff --git a/doc/src/sgml/postgres-fdw.sgml b/doc/src/sgml/postgres-fdw.sgml index 54b5e98a0e3..a46fd750f68 100644 --- a/doc/src/sgml/postgres-fdw.sgml +++ b/doc/src/sgml/postgres-fdw.sgml @@ -544,7 +544,7 @@ postgres_fdw likewise establishes remote session settings - for various parameters: + for various parameters: diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index a0e1f78bfc8..09893d96b57 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -1586,7 +1586,7 @@ PostgreSQL is tls-server-end-point. user-supplied password in the transmitted password hash. While this prevents the password hash from being successfully retransmitted in a later session, it does not prevent a fake server between the real - server and client from passing through the server's random value + server and client from passing through the server's random value and successfully authenticating. diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml index dd6bce57d2b..830e87fc6ae 100644 --- a/doc/src/sgml/ref/pg_basebackup.sgml +++ b/doc/src/sgml/ref/pg_basebackup.sgml @@ -327,7 +327,7 @@ PostgreSQL documentation When tar format mode is used, the write-ahead log files will be - written to a separate file named pg_wal.tar + written to a separate file named pg_wal.tar (if the server is a version earlier than 10, the file will be named pg_xlog.tar). diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index e9715d5cf7c..4d91eeb0ff4 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -260,7 +260,7 @@ GRANT EXECUTE ON function pg_catalog.pg_ls_dir(text, boolean, boolean) TO rewind GRANT EXECUTE ON function pg_catalog.pg_stat_file(text, boolean) TO rewind_user; GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text) TO rewind_user; GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, boolean) TO rewind_user; - + diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index c896882dd12..f6d423ee13e 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -796,7 +796,7 @@ psql --username=postgres --file=script.sql postgres 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. + likewise not be transferred to the new cluster. diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index fde9dbc1346..388dc7e9662 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -643,7 +643,7 @@ psql: could not connect to server: No such file or directory amount of anonymous mmap shared memory. Alternatively, a single large System V shared memory region can be used (see ). - + In addition a significant number of semaphores, which can be either System V or POSIX style, are created at server startup. Currently, POSIX semaphores are used on Linux and FreeBSD systems while other diff --git a/doc/src/sgml/spgist.sgml b/doc/src/sgml/spgist.sgml index 126d1f6c156..d43ef139198 100644 --- a/doc/src/sgml/spgist.sgml +++ b/doc/src/sgml/spgist.sgml @@ -160,7 +160,7 @@ <-> - + text_ops -- 2.39.5