Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit525115a

Browse files
committed
doc: Spell checking
1 parent9ffe128 commit525115a

File tree

14 files changed

+28
-28
lines changed

14 files changed

+28
-28
lines changed

‎doc/src/sgml/bki.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -655,7 +655,7 @@
655655
<filename>reformat_dat_file.pl</filename> can be adapted to perform
656656
many kinds of bulk changes. Look for its block comments showing where
657657
one-off code can be inserted. In the following example, we are going
658-
to consolidate twoboolean fields in <structname>pg_proc</structname>
658+
to consolidate twoBoolean fields in <structname>pg_proc</structname>
659659
into a char field:
660660

661661
<orderedlist>

‎doc/src/sgml/fdwhandler.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -461,7 +461,7 @@ AddForeignUpdateTargets(PlannerInfo *root,
461461
<structfield>vartype</structfield> = <type>RECORD</type>,
462462
and <literal>wholerow<replaceable>N</replaceable></literal>
463463
for a whole-row <structname>Var</structname> with
464-
<structfield>vartype</structfield> equal to the table's declaredrowtype.
464+
<structfield>vartype</structfield> equal to the table's declaredrow type.
465465
Re-use these names when you can (the planner will combine duplicate
466466
requests for identical junk columns). If you need another kind of
467467
junk column besides these, it might be wise to choose a name prefixed

‎doc/src/sgml/func.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24954,8 +24954,8 @@ SELECT collation for ('foo' COLLATE "de_DE");
2495424954
sending a <systemitem>SIGHUP</systemitem> signal to the postmaster
2495524955
process, which in turn sends <systemitem>SIGHUP</systemitem> to each
2495624956
of its children.) You can use the
24957-
<link linkend="view-pg-file-settings">pg_file_settings</link> and
24958-
<link linkend="view-pg-hba-file-rules">pg_hba_file_rules</link> views
24957+
<link linkend="view-pg-file-settings"><structname>pg_file_settings</structname></link> and
24958+
<link linkend="view-pg-hba-file-rules"><structname>pg_hba_file_rules</structname></link> views
2495924959
to check the configuration files for possible errors, before reloading.
2496024960
</para></entry>
2496124961
</row>

‎doc/src/sgml/gist.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -374,8 +374,8 @@ my_consistent(PG_FUNCTION_ARGS)
374374
<para>
375375
Depending on which operators you have included in the class, the data
376376
type of <varname>query</varname> could vary with the operator, since it will
377-
be whatever type is on therighthand side of the operator, which might
378-
be different from the indexed data type appearing on thelefthand side.
377+
be whatever type is on theright-hand side of the operator, which might
378+
be different from the indexed data type appearing on theleft-hand side.
379379
(The above code skeleton assumes that only one type is possible; if
380380
not, fetching the <varname>query</varname> argument value would have to depend
381381
on the operator.) It is recommended that the SQL declaration of

‎doc/src/sgml/indexam.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -310,7 +310,7 @@ aminsert (Relation indexRelation,
310310
</para>
311311

312312
<para>
313-
The <literal>indexUnchanged</literal>boolean value gives a hint
313+
The <literal>indexUnchanged</literal>Boolean value gives a hint
314314
about the nature of the tuple to be indexed. When it is true,
315315
the tuple is a duplicate of some existing tuple in the index. The
316316
new tuple is a logically unchanged successor MVCC tuple version. This
@@ -493,7 +493,7 @@ amproperty (Oid index_oid, int attno,
493493
code, it's better to inspect <parameter>prop</parameter>.
494494
If the <structfield>amproperty</structfield> method returns <literal>true</literal> then
495495
it has determined the property test result: it must set <literal>*res</literal>
496-
to theboolean value to return, or set <literal>*isnull</literal>
496+
to theBoolean value to return, or set <literal>*isnull</literal>
497497
to <literal>true</literal> to return a NULL. (Both of the referenced variables
498498
are initialized to <literal>false</literal> before the call.)
499499
If the <structfield>amproperty</structfield> method returns <literal>false</literal> then

‎doc/src/sgml/json.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -617,7 +617,7 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
617617
<para>
618618
<command>UPDATE</command> statements may use subscripting in the
619619
<literal>SET</literal> clause to modify <type>jsonb</type> values. Subscript
620-
paths must betraversible for all affected values insofar as they exist. For
620+
paths must betraversable for all affected values insofar as they exist. For
621621
instance, the path <literal>val['a']['b']['c']</literal> can be traversed all
622622
the way to <literal>c</literal> if every <literal>val</literal>,
623623
<literal>val['a']</literal>, and <literal>val['a']['b']</literal> is an

‎doc/src/sgml/libpq.sgml‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1719,7 +1719,7 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname
17191719
There is no environment variable equivalent to this option, and no
17201720
facility for looking it up in <filename>.pgpass</filename>. It can be
17211721
used in a service file connection definition. Users with
1722-
more sophisticated uses should consider usingopenssl engines and
1722+
more sophisticated uses should consider using<productname>OpenSSL</productname> engines and
17231723
tools like PKCS#11 or USB crypto offload devices.
17241724
</para>
17251725
</listitem>
@@ -5032,7 +5032,7 @@ int PQflush(PGconn *conn);
50325032
<para>
50335033
While the pipeline API was introduced in
50345034
<productname>PostgreSQL</productname> 14, it is a client-side feature
5035-
which doesn't require special server support, and works on any server
5035+
which doesn't require special server support and works on any server
50365036
that supports the v3 extended query protocol.
50375037
</para>
50385038

@@ -5451,8 +5451,8 @@ int PQsendFlushRequest(PGconn *conn);
54515451
are being performed in rapid succession. There is usually less benefit
54525452
in using pipelined commands when each query takes many multiples of the client/server
54535453
round-trip time to execute. A 100-statement operation run on a server
5454-
300ms round-trip-time away would take 30 seconds in network latency alone
5455-
without pipelining; with pipelining it may spend as little as 0.3s waiting for
5454+
300 ms round-trip-time away would take 30 seconds in network latency alone
5455+
without pipelining; with pipelining it may spend as little as 0.3 s waiting for
54565456
results from the server.
54575457
</para>
54585458

@@ -7109,9 +7109,9 @@ defaultNoticeProcessor(void *arg, const char *message)
71097109
<para>
71107110
Each registered event handler is associated with two pieces of data,
71117111
known to <application>libpq</application> only as opaque <literal>void *</literal>
7112-
pointers. There is a <firstterm>passthrough</firstterm> pointer that is provided
7112+
pointers. There is a <firstterm>pass-through</firstterm> pointer that is provided
71137113
by the application when the event handler is registered with a
7114-
<structname>PGconn</structname>. Thepassthrough pointer never changes for the
7114+
<structname>PGconn</structname>. Thepass-through pointer never changes for the
71157115
life of the <structname>PGconn</structname> and all <structname>PGresult</structname>s
71167116
generated from it; so if used, it must point to long-lived data.
71177117
In addition there is an <firstterm>instance data</firstterm> pointer, which starts
@@ -7121,9 +7121,9 @@ defaultNoticeProcessor(void *arg, const char *message)
71217121
<xref linkend="libpq-PQsetInstanceData"/>,
71227122
<xref linkend="libpq-PQresultInstanceData"/> and
71237123
<function>PQsetResultInstanceData</function> functions. Note that
7124-
unlike thepassthrough pointer, instance data of a <structname>PGconn</structname>
7124+
unlike thepass-through pointer, instance data of a <structname>PGconn</structname>
71257125
is not automatically inherited by <structname>PGresult</structname>s created from
7126-
it. <application>libpq</application> does not know whatpassthrough
7126+
it. <application>libpq</application> does not know whatpass-through
71277127
and instance data pointers point to (if anything) and will never attempt
71287128
to free them &mdash; that is the responsibility of the event handler.
71297129
</para>

‎doc/src/sgml/logicaldecoding.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1232,7 +1232,7 @@ stream_commit_cb(...); &lt;-- commit of the streamed transaction
12321232
Similar to spill-to-disk behavior, streaming is triggered when the total
12331233
amount of changes decoded from the WAL (for all in-progress transactions)
12341234
exceeds the limit defined by <varname>logical_decoding_work_mem</varname> setting.
1235-
At that point, the largesttoplevel transaction (measured by the amount of memory
1235+
At that point, the largesttop-level transaction (measured by the amount of memory
12361236
currently used for decoded changes) is selected and streamed. However, in
12371237
some cases we still have to spill to disk even if streaming is enabled
12381238
because we exceed the memory threshold but still have not decoded the

‎doc/src/sgml/monitoring.sgml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2642,7 +2642,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
26422642
Number of transactions spilled to disk once the memory used by
26432643
logical decoding to decode changes from WAL has exceeded
26442644
<literal>logical_decoding_work_mem</literal>. The counter gets
2645-
incremented for bothtoplevel transactions and subtransactions.
2645+
incremented for bothtop-level transactions and subtransactions.
26462646
</para></entry>
26472647
</row>
26482648

@@ -2679,7 +2679,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
26792679
plugin after the memory used by logical decoding to decode changes
26802680
from WAL for this slot has exceeded
26812681
<literal>logical_decoding_work_mem</literal>. Streaming only
2682-
works withtoplevel transactions (subtransactions can't be streamed
2682+
works withtop-level transactions (subtransactions can't be streamed
26832683
independently), so the counter is not incremented for subtransactions.
26842684
</para></entry>
26852685
</row>
@@ -2715,7 +2715,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
27152715
</para>
27162716
<para>
27172717
Number of decoded transactions sent to the decoding output plugin for
2718-
this slot. This countstoplevel transactions only, and is not incremented
2718+
this slot. This countstop-level transactions only, and is not incremented
27192719
for subtransactions. Note that this includes the transactions that are
27202720
streamed and/or spilled.
27212721
</para></entry>

‎doc/src/sgml/pgstatstatements.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@
4343
The statistics gathered by the module are made available via a
4444
view named <structname>pg_stat_statements</structname>. This view
4545
contains one row for each distinct combination of database ID, user
46-
ID, query ID and whether it's a toplevel statement or not (up to
46+
ID, query ID and whether it's a top-level statement or not (up to
4747
the maximum number of distinct statements that the module can track).
4848
The columns of the view are shown in
4949
<xref linkend="pgstatstatements-columns"/>.
@@ -89,7 +89,7 @@
8989
<structfield>toplevel</structfield> <type>bool</type>
9090
</para>
9191
<para>
92-
True if the query was executed as a toplevel statement
92+
True if the query was executed as a top-level statement
9393
(always true if <varname>pg_stat_statements.track</varname> is set to
9494
<literal>top</literal>)
9595
</para></entry>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp