diff options
| -rw-r--r-- | doc/src/sgml/bki.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/fdwhandler.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/func.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/gist.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/indexam.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/json.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/libpq.sgml | 16 | ||||
| -rw-r--r-- | doc/src/sgml/logicaldecoding.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/monitoring.sgml | 6 | ||||
| -rw-r--r-- | doc/src/sgml/pgstatstatements.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/ref/alter_table.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/ref/psql-ref.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/wal.sgml | 2 |
13 files changed, 26 insertions, 26 deletions
diff --git a/doc/src/sgml/bki.sgml b/doc/src/sgml/bki.sgml index f32208b5504..f900a01b824 100644 --- a/doc/src/sgml/bki.sgml +++ b/doc/src/sgml/bki.sgml @@ -669,7 +669,7 @@ <filename>reformat_dat_file.pl</filename> can be adapted to perform many kinds of bulk changes. Look for its block comments showing where one-off code can be inserted. In the following example, we are going - to consolidate two boolean fields in <structname>pg_proc</structname> + to consolidate two Boolean fields in <structname>pg_proc</structname> into a char field: <orderedlist> diff --git a/doc/src/sgml/fdwhandler.sgml b/doc/src/sgml/fdwhandler.sgml index d1194def820..c21fe67eb7a 100644 --- a/doc/src/sgml/fdwhandler.sgml +++ b/doc/src/sgml/fdwhandler.sgml @@ -461,7 +461,7 @@ AddForeignUpdateTargets(PlannerInfo *root, <structfield>vartype</structfield> = <type>RECORD</type>, and <literal>wholerow<replaceable>N</replaceable></literal> for a whole-row <structname>Var</structname> with - <structfield>vartype</structfield> equal to the table's declared rowtype. + <structfield>vartype</structfield> equal to the table's declared row type. Re-use these names when you can (the planner will combine duplicate requests for identical junk columns). If you need another kind of junk column besides these, it might be wise to choose a name prefixed diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 6388385edc5..ac6347a9711 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -24954,8 +24954,8 @@ SELECT collation for ('foo' COLLATE "de_DE"); sending a <systemitem>SIGHUP</systemitem> signal to the postmaster process, which in turn sends <systemitem>SIGHUP</systemitem> to each of its children.) You can use the - <link linkend="view-pg-file-settings">pg_file_settings</link> and - <link linkend="view-pg-hba-file-rules">pg_hba_file_rules</link> views + <link linkend="view-pg-file-settings"><structname>pg_file_settings</structname></link> and + <link linkend="view-pg-hba-file-rules"><structname>pg_hba_file_rules</structname></link> views to check the configuration files for possible errors, before reloading. </para></entry> </row> diff --git a/doc/src/sgml/gist.sgml b/doc/src/sgml/gist.sgml index f22efd1f6e8..c79ce850e94 100644 --- a/doc/src/sgml/gist.sgml +++ b/doc/src/sgml/gist.sgml @@ -374,8 +374,8 @@ my_consistent(PG_FUNCTION_ARGS) <para> Depending on which operators you have included in the class, the data type of <varname>query</varname> could vary with the operator, since it will - be whatever type is on the righthand side of the operator, which might - be different from the indexed data type appearing on the lefthand side. + be whatever type is on the right-hand side of the operator, which might + be different from the indexed data type appearing on the left-hand side. (The above code skeleton assumes that only one type is possible; if not, fetching the <varname>query</varname> argument value would have to depend on the operator.) It is recommended that the SQL declaration of diff --git a/doc/src/sgml/indexam.sgml b/doc/src/sgml/indexam.sgml index ceee5f3580c..cf359fa9ffd 100644 --- a/doc/src/sgml/indexam.sgml +++ b/doc/src/sgml/indexam.sgml @@ -310,7 +310,7 @@ aminsert (Relation indexRelation, </para> <para> - The <literal>indexUnchanged</literal> boolean value gives a hint + The <literal>indexUnchanged</literal> Boolean value gives a hint about the nature of the tuple to be indexed. When it is true, the tuple is a duplicate of some existing tuple in the index. The new tuple is a logically unchanged successor MVCC tuple version. This @@ -493,7 +493,7 @@ amproperty (Oid index_oid, int attno, code, it's better to inspect <parameter>prop</parameter>. If the <structfield>amproperty</structfield> method returns <literal>true</literal> then it has determined the property test result: it must set <literal>*res</literal> - to the boolean value to return, or set <literal>*isnull</literal> + to the Boolean value to return, or set <literal>*isnull</literal> to <literal>true</literal> to return a NULL. (Both of the referenced variables are initialized to <literal>false</literal> before the call.) If the <structfield>amproperty</structfield> method returns <literal>false</literal> then diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index 1b5103e2694..673c70c3bb8 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -617,7 +617,7 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu <para> <command>UPDATE</command> statements may use subscripting in the <literal>SET</literal> clause to modify <type>jsonb</type> values. Subscript - paths must be traversible for all affected values insofar as they exist. For + paths must be traversable for all affected values insofar as they exist. For instance, the path <literal>val['a']['b']['c']</literal> can be traversed all the way to <literal>c</literal> if every <literal>val</literal>, <literal>val['a']</literal>, and <literal>val['a']['b']</literal> is an diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 2e4f615a659..56689ba8730 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1719,7 +1719,7 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname There is no environment variable equivalent to this option, and no facility for looking it up in <filename>.pgpass</filename>. It can be used in a service file connection definition. Users with - more sophisticated uses should consider using openssl engines and + more sophisticated uses should consider using <productname>OpenSSL</productname> engines and tools like PKCS#11 or USB crypto offload devices. </para> </listitem> @@ -5032,7 +5032,7 @@ int PQflush(PGconn *conn); <para> While the pipeline API was introduced in <productname>PostgreSQL</productname> 14, it is a client-side feature - which doesn't require special server support, and works on any server + which doesn't require special server support and works on any server that supports the v3 extended query protocol. </para> @@ -5451,8 +5451,8 @@ int PQsendFlushRequest(PGconn *conn); are being performed in rapid succession. There is usually less benefit in using pipelined commands when each query takes many multiples of the client/server round-trip time to execute. A 100-statement operation run on a server - 300ms round-trip-time away would take 30 seconds in network latency alone - without pipelining; with pipelining it may spend as little as 0.3s waiting for + 300 ms round-trip-time away would take 30 seconds in network latency alone + without pipelining; with pipelining it may spend as little as 0.3 s waiting for results from the server. </para> @@ -7109,9 +7109,9 @@ defaultNoticeProcessor(void *arg, const char *message) <para> Each registered event handler is associated with two pieces of data, known to <application>libpq</application> only as opaque <literal>void *</literal> - pointers. There is a <firstterm>passthrough</firstterm> pointer that is provided + pointers. There is a <firstterm>pass-through</firstterm> pointer that is provided by the application when the event handler is registered with a - <structname>PGconn</structname>. The passthrough pointer never changes for the + <structname>PGconn</structname>. The pass-through pointer never changes for the life of the <structname>PGconn</structname> and all <structname>PGresult</structname>s generated from it; so if used, it must point to long-lived data. In addition there is an <firstterm>instance data</firstterm> pointer, which starts @@ -7121,9 +7121,9 @@ defaultNoticeProcessor(void *arg, const char *message) <xref linkend="libpq-PQsetInstanceData"/>, <xref linkend="libpq-PQresultInstanceData"/> and <function>PQsetResultInstanceData</function> functions. Note that - unlike the passthrough pointer, instance data of a <structname>PGconn</structname> + unlike the pass-through pointer, instance data of a <structname>PGconn</structname> is not automatically inherited by <structname>PGresult</structname>s created from - it. <application>libpq</application> does not know what passthrough + it. <application>libpq</application> does not know what pass-through and instance data pointers point to (if anything) and will never attempt to free them — that is the responsibility of the event handler. </para> diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml index 002efc86b43..89b8090b79f 100644 --- a/doc/src/sgml/logicaldecoding.sgml +++ b/doc/src/sgml/logicaldecoding.sgml @@ -1251,7 +1251,7 @@ stream_commit_cb(...); <-- commit of the streamed transaction Similar to spill-to-disk behavior, streaming is triggered when the total amount of changes decoded from the WAL (for all in-progress transactions) exceeds the limit defined by <varname>logical_decoding_work_mem</varname> setting. - At that point, the largest toplevel transaction (measured by the amount of memory + At that point, the largest top-level transaction (measured by the amount of memory currently used for decoded changes) is selected and streamed. However, in some cases we still have to spill to disk even if streaming is enabled because we exceed the memory threshold but still have not decoded the diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 643e1ad49fd..74a58a916c1 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -2647,7 +2647,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i Number of transactions spilled to disk once the memory used by logical decoding to decode changes from WAL has exceeded <literal>logical_decoding_work_mem</literal>. The counter gets - incremented for both toplevel transactions and subtransactions. + incremented for both top-level transactions and subtransactions. </para></entry> </row> @@ -2684,7 +2684,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i plugin after the memory used by logical decoding to decode changes from WAL for this slot has exceeded <literal>logical_decoding_work_mem</literal>. Streaming only - works with toplevel transactions (subtransactions can't be streamed + works with top-level transactions (subtransactions can't be streamed independently), so the counter is not incremented for subtransactions. </para></entry> </row> @@ -2720,7 +2720,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i </para> <para> Number of decoded transactions sent to the decoding output plugin for - this slot. This counts toplevel transactions only, and is not incremented + this slot. This counts top-level transactions only, and is not incremented for subtransactions. Note that this includes the transactions that are streamed and/or spilled. </para></entry> diff --git a/doc/src/sgml/pgstatstatements.sgml b/doc/src/sgml/pgstatstatements.sgml index 542b197282c..70b28a92c10 100644 --- a/doc/src/sgml/pgstatstatements.sgml +++ b/doc/src/sgml/pgstatstatements.sgml @@ -43,7 +43,7 @@ The statistics gathered by the module are made available via a view named <structname>pg_stat_statements</structname>. This view contains one row for each distinct combination of database ID, user - ID, query ID and whether it's a top level statement or not (up to + ID, query ID and whether it's a top-level statement or not (up to the maximum number of distinct statements that the module can track). The columns of the view are shown in <xref linkend="pgstatstatements-columns"/>. @@ -89,7 +89,7 @@ <structfield>toplevel</structfield> <type>bool</type> </para> <para> - True if the query was executed as a top level statement + True if the query was executed as a top-level statement (always true if <varname>pg_stat_statements.track</varname> is set to <literal>top</literal>) </para></entry> diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index c5e5e84e06b..1c7f48938bc 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -1002,7 +1002,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM </para> <para> If <literal>FINALIZE</literal> is specified, a previous - <literal>DETACH CONCURRENTLY</literal> invocation that was cancelled or + <literal>DETACH CONCURRENTLY</literal> invocation that was canceled or interrupted is completed. At most one partition in a partitioned table can be pending detach at a time. diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index da533068572..fcab5c0d51a 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -2430,7 +2430,7 @@ hello 10 </para> <para> The <command>\if</command> and <command>\elif</command> commands read - their argument(s) and evaluate them as a boolean expression. If the + their argument(s) and evaluate them as a Boolean expression. If the expression yields <literal>true</literal> then processing continues normally; otherwise, lines are skipped until a matching <command>\elif</command>, <command>\else</command>, diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 60f066d2473..24e1c89503c 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -836,7 +836,7 @@ <acronym>WAL</acronym> logs are stored in the directory <filename>pg_wal</filename> under the data directory, as a set of segment files, normally each 16 MB in size (but the size can be changed - by altering the <option>--wal-segsize</option> initdb option). Each segment is + by altering the <option>--wal-segsize</option> <application>initdb</application> option). Each segment is divided into pages, normally 8 kB each (this size can be changed via the <option>--with-wal-blocksize</option> configure option). The log record headers are described in <filename>access/xlogrecord.h</filename>; the record |