diff --git a/doc/src/sgml/btree.sgml b/doc/src/sgml/btree.sgml index f569f93f352..a9200ee52e6 100644 --- a/doc/src/sgml/btree.sgml +++ b/doc/src/sgml/btree.sgml @@ -664,7 +664,7 @@ options(relopts local_relopts *) returns certain implementation-level heuristics will fail to identify and delete even one garbage index tuple (in which case a page split or deduplication pass resolves the issue of an incoming new tuple not - fitting on a leaf page). The worst case number of versions that + fitting on a leaf page). The worst-case number of versions that any index scan must traverse (for any single logical row) is an important contributor to overall system responsiveness and throughput. A bottom-up index deletion pass targets suspected @@ -706,7 +706,7 @@ options(relopts local_relopts *) returns This is expected with any B-Tree index that is subject to significant version churn from UPDATEs that rarely or never logically modify the columns that the index covers. - The average and worst case number of versions per logical row can + The average and worst-case number of versions per logical row can be kept low purely through targeted incremental deletion passes. It's quite possible that the on-disk size of certain indexes will never increase by even one single page/block despite @@ -811,7 +811,7 @@ options(relopts local_relopts *) returns constraints) to use deduplication. This allows leaf pages to temporarily absorb extra version churn duplicates. Deduplication in unique indexes augments bottom-up index deletion, - especially in cases where a long-running transactions holds a + especially in cases where a long-running transaction holds a snapshot that blocks garbage collection. The goal is to buy time for the bottom-up index deletion strategy to become effective again. Delaying page splits until a single long-running diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 7523a25b3dc..688e7781737 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -13114,7 +13114,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx pg_stats_ext_exprs is also designed to present the information in a more readable format than the underlying catalogs — at the cost that its schema must be extended whenever the structure - of statistics in pg_statistic changes. + of statistics in pg_statistic_ext changes. diff --git a/doc/src/sgml/ref/alter_subscription.sgml b/doc/src/sgml/ref/alter_subscription.sgml index 220b0de2aff..6d256b694e8 100644 --- a/doc/src/sgml/ref/alter_subscription.sgml +++ b/doc/src/sgml/ref/alter_subscription.sgml @@ -65,8 +65,9 @@ ALTER SUBSCRIPTION name RENAME TO < Commands ALTER SUBSCRIPTION ... REFRESH PUBLICATION and - ALTER SUBSCRIPTION ... {SET|ADD|DROP} PUBLICATION ... with refresh - option as true cannot be executed inside a transaction block. + ALTER SUBSCRIPTION ... {SET|ADD|DROP} PUBLICATION ... + with refresh option as true cannot be + executed inside a transaction block. diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index e62742850a3..6604575f362 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -283,7 +283,7 @@ PostgreSQL documentation By default, initdb will write instructions for how to start the cluster at the end of its output. This option causes those instructions to be left out. This is primarily intended for use - by tools that wrap initdb in platform specific + by tools that wrap initdb in platform-specific behavior, where those instructions are likely to be incorrect. diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 13a24a05e50..60069c15626 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1936,11 +1936,11 @@ testdb=> The status of each kind of extended statistics is shown in a column named after its statistic kind (e.g. Ndistinct). - "defined" means that it was requested when creating the statistics, - and NULL means it wasn't requested. - You can use pg_stats_ext if you'd like to know whether - ANALYZE was run and statistics are available to the - planner. + defined means that it was requested when creating + the statistics, and NULL means it wasn't requested. + You can use pg_stats_ext if you'd like to + know whether ANALYZE + was run and statistics are available to the planner. diff --git a/doc/src/sgml/spgist.sgml b/doc/src/sgml/spgist.sgml index 18f1f3cdbd8..00432512de9 100644 --- a/doc/src/sgml/spgist.sgml +++ b/doc/src/sgml/spgist.sgml @@ -875,8 +875,9 @@ typedef struct spgLeafConsistentOut Note: the compress method is only applied to - values to be stored. The consistent methods receive query scankeys - unchanged, without transformation using compress. + values to be stored. The consistent methods receive query + scankeys unchanged, without transformation + using compress. diff --git a/doc/src/sgml/test-decoding.sgml b/doc/src/sgml/test-decoding.sgml index fe7c9783fac..cf736bd41af 100644 --- a/doc/src/sgml/test-decoding.sgml +++ b/doc/src/sgml/test-decoding.sgml @@ -40,8 +40,8 @@ postgres=# SELECT * FROM pg_logical_slot_get_changes('test_slot', NULL, NULL, 'i - We can also get the changes of the in-progress transaction and the typical - output, might be: + We can also get the changes of the in-progress transaction, and the typical + output might be: postgres[33712]=#* SELECT * FROM pg_logical_slot_get_changes('test_slot', NULL, NULL, 'stream-changes', '1');