From 8522f21400570fdf6af38c32a2522a5465dccfd5 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Tue, 8 Jul 2014 23:29:09 -0400 Subject: [PATCH] Fix whitespace --- doc/src/sgml/datatype.sgml | 2 +- doc/src/sgml/func.sgml | 10 +++++----- doc/src/sgml/gin.sgml | 4 ++-- doc/src/sgml/libpq.sgml | 2 +- doc/src/sgml/pgcrypto.sgml | 2 +- doc/src/sgml/pgprewarm.sgml | 2 +- doc/src/sgml/plpgsql.sgml | 4 ++-- doc/src/sgml/recovery-config.sgml | 2 +- doc/src/sgml/ref/alter_system.sgml | 6 +++--- doc/src/sgml/ref/create_aggregate.sgml | 2 +- doc/src/sgml/ref/create_table.sgml | 2 +- doc/src/sgml/ref/pg_basebackup.sgml | 2 +- doc/src/sgml/ref/psql-ref.sgml | 2 +- 13 files changed, 21 insertions(+), 21 deletions(-) diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 828ed9e092..790ba9e3dd 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -4496,7 +4496,7 @@ SELECT * FROM pg_attribute the write-ahead log stream. It is printed as two hexadecimal numbers of up to 8 digits each, separated by a slash; for example, 16/B374D848. The pg_lsn type supports the - standard comparison operators, like = and + standard comparison operators, like = and >. Two LSNs can be subtracted using the - operator; the result is the number of bytes separating those write-ahead log positions. diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 6207ef782d..6c4a15515b 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -10160,8 +10160,8 @@ table2-mapping The standard comparison operators shown in are available for - jsonb, but not for json. They follow the + linkend="functions-comparison-table"> are available for + jsonb, but not for json. They follow the ordering rules for btree operations outlined at . @@ -10668,9 +10668,9 @@ table2-mapping select * from json_to_record('{"a":1,"b":[1,2,3],"c":"bar"}') as x(a int, b text, d text) - a | b | d + a | b | d ---+---------+--- - 1 | [1,2,3] | + 1 | [1,2,3] | @@ -14006,7 +14006,7 @@ AND *>=. These operators compare the internal binary representation of the two rows. Two rows might have a different binary representation even - though comparisons of the two rows with the equality operator is true. + though comparisons of the two rows with the equality operator is true. The ordering of rows under these comparision operators is deterministic but not otherwise meaningful. These operators are used internally for materialized views and might be useful for other specialized purposes diff --git a/doc/src/sgml/gin.sgml b/doc/src/sgml/gin.sgml index 1cbc73c70c..80a578dee8 100644 --- a/doc/src/sgml/gin.sgml +++ b/doc/src/sgml/gin.sgml @@ -559,7 +559,7 @@ triConsistent alone is sufficient. However, if the boolean variant is significantly cheaper to calculate, it can be advantageous to provide both. If only the boolean variant is provided, some optimizations that depend on - refuting index items before fetching all the keys are disabled. + refuting index items before fetching all the keys are disabled. @@ -628,7 +628,7 @@ When GIN_MAYBE values are present, the function should only return GIN_TRUE if the item matches whether or not the index item contains the corresponding query keys. Likewise, the function must - return GIN_FALSE only if the item does not match, whether or not it + return GIN_FALSE only if the item does not match, whether or not it contains the GIN_MAYBE keys. If the result depends on the GIN_MAYBE entries, i.e. the match cannot be confirmed or refuted based on the known query keys, the function must return GIN_MAYBE. diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index e10ccec9f1..0d98bb0420 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -7200,7 +7200,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*) - Note that the client's ~/.postgresql/root.crt lists the top-level CAs + Note that the client's ~/.postgresql/root.crt lists the top-level CAs that are considered trusted for signing server certificates. In principle it need not list the CA that signed the client's certificate, though in most cases that CA would also be trusted for server certificates. diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml index 2446879142..f93e7f9717 100644 --- a/doc/src/sgml/pgcrypto.sgml +++ b/doc/src/sgml/pgcrypto.sgml @@ -95,7 +95,7 @@ hmac(data bytea, key text, type text) returns bytea - The algorithms in crypt() differ from the usual + The algorithms in crypt() differ from the usual MD5 or SHA1 hashing algorithms in the following respects: diff --git a/doc/src/sgml/pgprewarm.sgml b/doc/src/sgml/pgprewarm.sgml index 2200d3df65..2989ac393e 100644 --- a/doc/src/sgml/pgprewarm.sgml +++ b/doc/src/sgml/pgprewarm.sgml @@ -25,7 +25,7 @@ pg_prewarm(regclass, mode text default 'buffer', fork text default 'main', The first argument is the relation to be prewarmed. The second argument is the prewarming method to be used, as further discussed below; the third - is the relation fork to be prewarmed, usually main. + is the relation fork to be prewarmed, usually main. The fourth argument is the first block number to prewarm (NULL is accepted as a synonym for zero). The fifth argument is the last block number to prewarm (NULL diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml index a549a24eae..4cb5868cda 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -4726,7 +4726,7 @@ a_output := a_output || $$ if v_$$ || referrer_keys.kind || $$ like '$$ These additional checks are enabled through the configuration variables - plpgsql.extra_warnings for warnings and + plpgsql.extra_warnings for warnings and plpgsql.extra_errors for errors. Both can be set either to a comma-separated list of checks, "none" or "all". The default is "none". Currently the list of available checks @@ -4736,7 +4736,7 @@ a_output := a_output || $$ if v_$$ || referrer_keys.kind || $$ like '$$ shadowed_variables - Checks if a declaration shadows a previously defined variable. + Checks if a declaration shadows a previously defined variable. diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml index 76f9d0327a..ba68ddd4eb 100644 --- a/doc/src/sgml/recovery-config.sgml +++ b/doc/src/sgml/recovery-config.sgml @@ -157,7 +157,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows following parameters can be used to specify an earlier stopping point. At most one of recovery_target, recovery_target_name, recovery_target_time, or - recovery_target_xid can be specified. + recovery_target_xid can be specified. diff --git a/doc/src/sgml/ref/alter_system.sgml b/doc/src/sgml/ref/alter_system.sgml index d11f6beeed..23c30efc8f 100644 --- a/doc/src/sgml/ref/alter_system.sgml +++ b/doc/src/sgml/ref/alter_system.sgml @@ -33,16 +33,16 @@ ALTER SYSTEM SET configuration_parameterpostgresql.auto.conf file. With DEFAULT, it removes a configuration entry from postgresql.auto.conf file. The values will be - effective after reload of server configuration (SIGHUP) or in next + effective after reload of server configuration (SIGHUP) or in next server start based on the type of configuration parameter modified. This command is not allowed inside transaction block or function. - + - See for other ways to set the parameters and + See for other ways to set the parameters and how they become effective. diff --git a/doc/src/sgml/ref/create_aggregate.sgml b/doc/src/sgml/ref/create_aggregate.sgml index ef1eaf85be..84a18b2796 100644 --- a/doc/src/sgml/ref/create_aggregate.sgml +++ b/doc/src/sgml/ref/create_aggregate.sgml @@ -447,7 +447,7 @@ SELECT col FROM tab ORDER BY col USING sortop LIMIT 1; The approximate average size (in bytes) of the aggregate's state - value, when using moving-aggregate mode. This works the same as + value, when using moving-aggregate mode. This works the same as state_data_size. diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 2a985b82e5..299cce8811 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -329,7 +329,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI Default expressions for the copied column definitions will only be - copied if INCLUDING DEFAULTS is specified. + copied if INCLUDING DEFAULTS is specified. Defaults that call database-modification functions, like nextval, create a linkage between the original and new tables. The diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml index 10c1743754..642fccf325 100644 --- a/doc/src/sgml/ref/pg_basebackup.sgml +++ b/doc/src/sgml/ref/pg_basebackup.sgml @@ -254,7 +254,7 @@ PostgreSQL documentation - Specifies the location for the transaction log directory. + Specifies the location for the transaction log directory. xlogdir must be an absolute path. The transaction log directory can only be specified when the backup is in plain mode. diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index ee6ec3a811..255e8cac14 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -951,7 +951,7 @@ testdb=> The command form \d+ is identical, except that more information is displayed: any comments associated with the columns of the table are shown, as is the presence of OIDs in the - table, the view definition if the relation is a view, a non-default + table, the view definition if the relation is a view, a non-default replica identity setting. -- 2.40.0