diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index d3458840fb..3ec7391ec5 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -7943,7 +7943,8 @@ SCRAM-SHA-256$<iteration count>:&l disk and apply at once after the transaction is committed on the publisher and received by the subscriber, p = apply changes directly using a parallel apply - worker if available (same as 't' if no worker is available) + worker if available (same as t if no worker is + available) diff --git a/doc/src/sgml/custom-rmgr.sgml b/doc/src/sgml/custom-rmgr.sgml index baf86b1c07..0d98229295 100644 --- a/doc/src/sgml/custom-rmgr.sgml +++ b/doc/src/sgml/custom-rmgr.sgml @@ -96,8 +96,8 @@ extern void RegisterCustomRmgr(RmgrId rmid, const RmgrData *rmgr); - The extension must remain in shared_preload_libraries as long as any - custom WAL records may exist in the system. Otherwise + The extension must remain in shared_preload_libraries + as long as any custom WAL records may exist in the system. Otherwise PostgreSQL will not be able to apply or decode the custom WAL records, which may prevent the server from starting. diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 54de81158b..25c62d7636 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -1506,9 +1506,9 @@ EXEC SQL TYPE serial_t IS long; - Any word you declare as a typedef cannot be used as an SQL keyword - in EXEC SQL commands later in the same program. - For example, this won't work: + Any word you declare as a typedef cannot be used as + an SQL keyword in EXEC SQL commands later in the same + program. For example, this won't work: EXEC SQL BEGIN DECLARE SECTION; typedef int start; diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml index f4b1f81189..8e0b2705d3 100644 --- a/doc/src/sgml/installation.sgml +++ b/doc/src/sgml/installation.sgml @@ -2743,8 +2743,8 @@ ninja install The default backend Meson uses is ninja and that should suffice for most use cases. However, if you'd like to fully integrate with Visual - Studio, you can set the to - vs. + Studio, you can set the BACKEND to + vs. diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml index cbd3aa804f..5af016cfa9 100644 --- a/doc/src/sgml/logicaldecoding.sgml +++ b/doc/src/sgml/logicaldecoding.sgml @@ -326,11 +326,12 @@ postgres=# select * from pg_logical_slot_get_changes('regression_slot', NULL, NU will work but only while the connection is alive (for example a node restart would break it). Then, the primary may delete system catalog rows that could be needed by the logical decoding on the standby (as it does - not know about the catalog_xmin on the standby). Existing logical slots - on standby also get invalidated if wal_level on the - primary is reduced to less than logical. + not know about the catalog_xmin on the standby). + Existing logical slots on standby also get invalidated if + wal_level on the primary is reduced to less than + logical. This is done as soon as the standby detects such a change in the WAL stream. - It means that, for walsenders which are lagging (if any), some WAL records up + It means that, for walsenders that are lagging (if any), some WAL records up to the wal_level parameter change on the primary won't be decoded. diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index b11d9a6ba3..3f854000f4 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -2437,11 +2437,12 @@ psql "dbname=postgres replication=database" -c "IDENTIFY_SYSTEM;" Int32 - The standby's current global xmin, excluding the catalog_xmin from any - replication slots. If both this value and the following - catalog_xmin are 0 this is treated as a notification that hot standby - feedback will no longer be sent on this connection. Later non-zero - messages may reinitiate the feedback mechanism. + The standby's current global xmin, excluding the + catalog_xmin from any replication slots. If both + this value and the following catalog_xmin + are 0, this is treated as a notification that hot standby feedback + will no longer be sent on this connection. Later non-zero messages + may reinitiate the feedback mechanism. @@ -2450,7 +2451,7 @@ psql "dbname=postgres replication=database" -c "IDENTIFY_SYSTEM;" Int32 - The epoch of the global xmin xid on the standby. + The epoch of the global xmin xid on the standby. @@ -2459,8 +2460,9 @@ psql "dbname=postgres replication=database" -c "IDENTIFY_SYSTEM;" Int32 - The lowest catalog_xmin of any replication slots on the standby. Set to 0 - if no catalog_xmin exists on the standby or if hot standby feedback is being + The lowest catalog_xmin of any replication + slots on the standby. Set to 0 if no catalog_xmin + exists on the standby or if hot standby feedback is being disabled. @@ -2470,7 +2472,7 @@ psql "dbname=postgres replication=database" -c "IDENTIFY_SYSTEM;" Int32 - The epoch of the catalog_xmin xid on the standby. + The epoch of the catalog_xmin xid on the standby. diff --git a/doc/src/sgml/xact.sgml b/doc/src/sgml/xact.sgml index b467660eee..1813cd0774 100644 --- a/doc/src/sgml/xact.sgml +++ b/doc/src/sgml/xact.sgml @@ -70,7 +70,7 @@ - In addition to vxid and xid, + In addition to vxid and xid, prepared transactions are also assigned Global Transaction Identifiers (GID). GIDs are string literals up to 200 bytes long, which must be unique amongst other currently @@ -121,7 +121,7 @@ Subtransactions can be started explicitly using the SAVEPOINT command, but can also be started in - other ways, such as PL/pgSQL's EXCEPTION clause. + other ways, such as PL/pgSQL's EXCEPTION clause. PL/Python and PL/TCL also support explicit subtransactions. Subtransactions can also be started from other subtransactions. The top-level transaction and its child subtransactions form a