index 2b2c70a26e5397a001274c30523c6a69812892ef..2f0def9b19aea4b5f01b65e1d660fc064f658d81 100644 (file)
@@ -9602,7 +9602,7 @@ SCRAM-SHA-256$<replaceable><iteration count></replaceable>:<replaceable>&l
</table>
<para>
- The <structname>pg_available_extensions</structname> view is readonly.
+ The <structname>pg_available_extensions</structname> view is read-only.
</para>
</sect1>
@@ -9726,8 +9726,8 @@ SCRAM-SHA-256$<replaceable><iteration count></replaceable>:<replaceable>&l
</table>
<para>
- The <structname>pg_available_extension_versions</structname> view is read
- only.
+ The <structname>pg_available_extension_versions</structname> view is
+ read-only.
</para>
</sect1>
@@ -10042,7 +10042,7 @@ SCRAM-SHA-256$<replaceable><iteration count></replaceable>:<replaceable>&l
</table>
<para>
- The <structname>pg_cursors</structname> view is readonly.
+ The <structname>pg_cursors</structname> view is read-only.
</para>
</sect1>
@@ -11164,7 +11164,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
</table>
<para>
- The <structname>pg_prepared_statements</structname> view is readonly.
+ The <structname>pg_prepared_statements</structname> view is read-only.
</para>
</sect1>
index 22af7dbf51b28478d159abc100c83b4f8521ca99..c43f214020553559dbd0783b564982eba0494244 100644 (file)
</para>
<para>
- Readonly transactions and transaction rollbacks need not wait for
+ Read-only transactions and transaction rollbacks need not wait for
replies from standby servers. Subtransaction commits do not wait for
responses from standby servers, only top-level commits. Long
running actions such as data loading or index building do not wait
... then some time later ...
LOG: consistent recovery state reached
-LOG: database system is ready to accept readonly connections
+LOG: database system is ready to accept read-only connections
</programlisting>
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
</para>
<para>
- Currently, temporary table creation is not allowed during readonly
+ Currently, temporary table creation is not allowed during read-only
transactions, so in some cases existing scripts will not run correctly.
This restriction might be relaxed in a later release. This is
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
<para>
Full knowledge of running transactions is required before snapshots
can be taken. Transactions that use large numbers of subtransactions
- (currently greater than 64) will delay the start of readonly
+ (currently greater than 64) will delay the start of read-only
connections until the completion of the longest running write transaction.
If this situation occurs, explanatory messages will be sent to the server log.
</para>
index d358bbe4a6a0719381aa07bfa9d2b11d3a9c85ef..cfdcb74221a12ca5faf1e71f8bccc486619d5841 100644 (file)
@@ -526,7 +526,7 @@ ERROR: could not serialize access due to concurrent update
transaction sees a completely stable view of the database. However,
this view will not necessarily always be consistent with some serial
(one at a time) execution of concurrent transactions of the same level.
- For example, even a readonly transaction at this level may see a
+ For example, even a read-only transaction at this level may see a
control record updated to show that a batch has been completed but
<emphasis>not</emphasis> see one of the detail records which is logically
part of the batch because it read an earlier revision of the control
index 9c2c98614aac52ac25cc910043dbaf58722f8ff9..63043ed8d1f2b99b2ea12e196aef58bab1ae9ea8 100644 (file)
PgStatPID = pgstat_start();
ereport(LOG,
- (errmsg("database system is ready to accept readonly connections")));
+ (errmsg("database system is ready to accept read-only connections")));
/* Report status */
AddToDataDirLockFile(LOCK_FILE_LINE_PM_STATUS, PM_STATUS_READY);