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

Commitd6c916f

Browse files
committed
Consistently use read-only instead of "read only"
This affects one message and some documentation that used the format"read only", unlike everything else that used read-only.Backpatch-through: 14Discussion:https://postgr.es/m/CABUevExuxKwn0YM3+wdSeQSvK6CRrJ-hewocGVX3R4-xVX4eMw@mail.gmail.com
1 parent76e38b3 commitd6c916f

File tree

4 files changed

+11
-11
lines changed

4 files changed

+11
-11
lines changed

‎doc/src/sgml/catalogs.sgml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9602,7 +9602,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
96029602
</table>
96039603

96049604
<para>
9605-
The <structname>pg_available_extensions</structname> view is readonly.
9605+
The <structname>pg_available_extensions</structname> view is read-only.
96069606
</para>
96079607
</sect1>
96089608

@@ -9726,8 +9726,8 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
97269726
</table>
97279727

97289728
<para>
9729-
The <structname>pg_available_extension_versions</structname> view is read
9730-
only.
9729+
The <structname>pg_available_extension_versions</structname> view is
9730+
read-only.
97319731
</para>
97329732
</sect1>
97339733

@@ -10042,7 +10042,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
1004210042
</table>
1004310043

1004410044
<para>
10045-
The <structname>pg_cursors</structname> view is readonly.
10045+
The <structname>pg_cursors</structname> view is read-only.
1004610046
</para>
1004710047

1004810048
</sect1>
@@ -11164,7 +11164,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
1116411164
</table>
1116511165

1116611166
<para>
11167-
The <structname>pg_prepared_statements</structname> view is readonly.
11167+
The <structname>pg_prepared_statements</structname> view is read-only.
1116811168
</para>
1116911169
</sect1>
1117011170

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1093,7 +1093,7 @@ primary_slot_name = 'node_a_slot'
10931093
</para>
10941094

10951095
<para>
1096-
Readonly transactions and transaction rollbacks need not wait for
1096+
Read-only transactions and transaction rollbacks need not wait for
10971097
replies from standby servers. Subtransaction commits do not wait for
10981098
responses from standby servers, only top-level commits. Long
10991099
running actions such as data loading or index building do not wait
@@ -1962,7 +1962,7 @@ LOG: entering standby mode
19621962
... then some time later ...
19631963

19641964
LOG: consistent recovery state reached
1965-
LOG: database system is ready to accept readonly connections
1965+
LOG: database system is ready to accept read-only connections
19661966
</programlisting>
19671967

19681968
Consistency information is recorded once per checkpoint on the primary.
@@ -2191,7 +2191,7 @@ HINT: You can then restart the server after making the necessary configuration
21912191
</para>
21922192

21932193
<para>
2194-
Currently, temporary table creation is not allowed during readonly
2194+
Currently, temporary table creation is not allowed during read-only
21952195
transactions, so in some cases existing scripts will not run correctly.
21962196
This restriction might be relaxed in a later release. This is
21972197
both an SQL Standard compliance issue and a technical issue.
@@ -2290,7 +2290,7 @@ HINT: You can then restart the server after making the necessary configuration
22902290
<para>
22912291
Full knowledge of running transactions is required before snapshots
22922292
can be taken. Transactions that use large numbers of subtransactions
2293-
(currently greater than 64) will delay the start of readonly
2293+
(currently greater than 64) will delay the start of read-only
22942294
connections until the completion of the longest running write transaction.
22952295
If this situation occurs, explanatory messages will be sent to the server log.
22962296
</para>

‎doc/src/sgml/mvcc.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -526,7 +526,7 @@ ERROR: could not serialize access due to concurrent update
526526
transaction sees a completely stable view of the database. However,
527527
this view will not necessarily always be consistent with some serial
528528
(one at a time) execution of concurrent transactions of the same level.
529-
For example, even a readonly transaction at this level may see a
529+
For example, even a read-only transaction at this level may see a
530530
control record updated to show that a batch has been completed but
531531
<emphasis>not</emphasis> see one of the detail records which is logically
532532
part of the batch because it read an earlier revision of the control

‎src/backend/postmaster/postmaster.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5199,7 +5199,7 @@ sigusr1_handler(SIGNAL_ARGS)
51995199
PgStatPID=pgstat_start();
52005200

52015201
ereport(LOG,
5202-
(errmsg("database system is ready to accept readonly connections")));
5202+
(errmsg("database system is ready to accept read-only connections")));
52035203

52045204
/* Report status */
52055205
AddToDataDirLockFile(LOCK_FILE_LINE_PM_STATUS,PM_STATUS_READY);

0 commit comments

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