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

Commitbf6e4c3

Browse files
committed
Trim trailing whitespace
1 parentddd7b22 commitbf6e4c3

File tree

10 files changed

+22
-22
lines changed

10 files changed

+22
-22
lines changed

‎doc/src/sgml/func.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4361,7 +4361,7 @@ SELECT (regexp_match('foobarbequebaz', 'bar.*que'))[1];
43614361
<para>
43624362
Some examples:
43634363
<programlisting>
4364-
SELECT regexp_matches('foo', 'not there');
4364+
SELECT regexp_matches('foo', 'not there');
43654365
regexp_matches
43664366
----------------
43674367
(0 rows)

‎doc/src/sgml/high-availability.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1175,7 +1175,7 @@ synchronous_standby_names = 'FIRST 2 (s1, s2, s3)'
11751175
An example of <varname>synchronous_standby_names</> for
11761176
a quorum-based multiple synchronous standbys is:
11771177
<programlisting>
1178-
synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
1178+
synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
11791179
</programlisting>
11801180
In this example, if four standby servers <literal>s1</>, <literal>s2</>,
11811181
<literal>s3</> and <literal>s4</> are running, transaction commits will

‎doc/src/sgml/libpq.sgml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5941,12 +5941,12 @@ char *PQencryptPasswordConn(PGconn *conn, const char *passwd, const char *user,
59415941
<listitem>
59425942
<para>
59435943
Prepares the md5-encrypted form of a <productname>PostgreSQL</> password.
5944-
<synopsis>
5944+
<synopsis>
59455945
char *PQencryptPassword(const char *passwd, const char *user);
5946-
</synopsis>
5947-
<function>PQencryptPassword</> is an older, deprecated version of
5946+
</synopsis>
5947+
<function>PQencryptPassword</> is an older, deprecated version of
59485948
<function>PQencryptPasswodConn</>. The difference is that
5949-
<function>PQencryptPassword</> does not
5949+
<function>PQencryptPassword</> does not
59505950
require a connection object, and <literal>md5</> is always used as the
59515951
encryption algorithm.
59525952
</para>

‎doc/src/sgml/monitoring.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -802,7 +802,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
802802
<row>
803803
<entry><structfield>backend_type</structfield></entry>
804804
<entry><type>text</type></entry>
805-
<entry>Type of current backend. Possible types are
805+
<entry>Type of current backend. Possible types are
806806
<literal>autovacuum launcher</>, <literal>autovacuum worker</>,
807807
<literal>background worker</>, <literal>background writer</>,
808808
<literal>client backend</>, <literal>checkpointer</>,
@@ -1827,7 +1827,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
18271827
the standby to catch up with the sending server assuming the current
18281828
rate of replay. Such a system would show similar times while new WAL is
18291829
being generated, but would differ when the sender becomes idle. In
1830-
particular, when the standby has caught up completely,
1830+
particular, when the standby has caught up completely,
18311831
<structname>pg_stat_replication</structname> shows the time taken to
18321832
write, flush and replay the most recent reported WAL location rather than
18331833
zero as some users might expect. This is consistent with the goal of

‎doc/src/sgml/parallel.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -275,7 +275,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
275275
<para>
276276
In a <emphasis>parallel sequential scan</>, the table's blocks will
277277
be divided among the cooperating processes. Blocks are handed out one
278-
at a time, so that access to the table remains sequential.
278+
at a time, so that access to the table remains sequential.
279279
</para>
280280
</listitem>
281281
<listitem>

‎doc/src/sgml/pgstattuple.sgml‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -119,13 +119,13 @@ free_percent | 1.95
119119
</table>
120120

121121
<note>
122-
<para>
123-
The <literal>table_len</literal> will always be greater than the sum
124-
of the <literal>tuple_len</literal>, <literal>dead_tuple_len</literal>
125-
and <literal>free_space</literal>. The difference is accounted for by
126-
fixed page overhead, the per-page table of pointers to tuples, and
127-
padding to ensure that tuples are correctly aligned.
128-
</para>
122+
<para>
123+
The <literal>table_len</literal> will always be greater than the sum
124+
of the <literal>tuple_len</literal>, <literal>dead_tuple_len</literal>
125+
and <literal>free_space</literal>. The difference is accounted for by
126+
fixed page overhead, the per-page table of pointers to tuples, and
127+
padding to ensure that tuples are correctly aligned.
128+
</para>
129129
</note>
130130

131131
<para>

‎doc/src/sgml/postgres-fdw.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -566,7 +566,7 @@
566566
</para>
567567
</listitem>
568568
</itemizedlist>
569-
These are less likely to be problematic than <varname>search_path</>, but
569+
These are less likely to be problematic than <varname>search_path</>, but
570570
can be handled with function <literal>SET</> options if the need arises.
571571
</para>
572572

‎doc/src/sgml/protocol.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1352,7 +1352,7 @@ general, while the next subsection gives more details on SCRAM-SHA-256.
13521352
<title>SASL Authentication Message Flow</title>
13531353

13541354
<step id="sasl-auth-begin">
1355-
<para>
1355+
<para>
13561356
To begin a SASL authentication exchange, the server sends an
13571357
AuthenticationSASL message. It includes a list of SASL authentication
13581358
mechanisms that the server can accept, in the server's preferred order.
@@ -1401,7 +1401,7 @@ ErrorMessage.
14011401
<para>
14021402
<firstterm>SCRAM-SHA-256</> (called just <firstterm>SCRAM</> from now on) is
14031403
the only implemented SASL mechanism, at the moment. It is described in detail
1404-
in RFC 7677 and RFC 5802.
1404+
in RFC 7677 and RFC 5802.
14051405
</para>
14061406

14071407
<para>

‎doc/src/sgml/ref/alter_table.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -185,7 +185,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
185185
table. Even if there is no <literal>NOT NULL</> constraint on the
186186
parent, such a constraint can still be added to individual partitions,
187187
if desired; that is, the children can disallow nulls even if the parent
188-
allows them, but not the other way around.
188+
allows them, but not the other way around.
189189
</para>
190190
</listitem>
191191
</varlistentry>
@@ -617,7 +617,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
617617
</para>
618618

619619
<para>
620-
<literal>SHARE UPDATE EXCLUSIVE</literal> lock will be taken for
620+
<literal>SHARE UPDATE EXCLUSIVE</literal> lock will be taken for
621621
fillfactor and autovacuum storage parameters, as well as the
622622
following planner related parameters:
623623
effective_io_concurrency, parallel_workers, seq_page_cost

‎doc/src/sgml/ref/copy.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -425,7 +425,7 @@ COPY <replaceable class="parameter">count</replaceable>
425425
</para>
426426

427427
<para>
428-
If row-level security is enabled for the table, the relevant
428+
If row-level security is enabled for the table, the relevant
429429
<command>SELECT</command> policies will apply to <literal>COPY
430430
<replaceable class="parameter">table</> TO</literal> statements.
431431
Currently, <command>COPY FROM</command> is not supported for tables

0 commit comments

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