v2-0001-Docs-Index-rebuilding-is-sometimes-skipped-along-.patch
application/octet-stream
Filename: v2-0001-Docs-Index-rebuilding-is-sometimes-skipped-along-.patch
Type: application/octet-stream
Part: 0
Patch
Format: format-patch
Series: patch v2-0001
Subject: Docs: Index rebuilding is sometimes skipped along with table rewriting
| File | + | − |
|---|---|---|
| doc/src/sgml/ref/alter_table.sgml | 2 | 1 |
From 33ef467fe03cd3b41d89b98b4cc2bf8974401f7f Mon Sep 17 00:00:00 2001
From: jcoleman <jtc331@gmail.com>
Date: Tue, 29 Mar 2022 13:56:39 +0000
Subject: [PATCH v2] Docs: Index rebuilding is sometimes skipped along with
table rewriting
In 367bc42 (for 9.2!) we "avoid index rebuild for no-rewrite ALTER TABLE
.. ALTER TYPE." This doesn't apply in all cases, but update the docs to
match so users don't conclude indexes must always be rewritten.
---
doc/src/sgml/ref/alter_table.sgml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 5c0735e08a..292efb67af 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -1366,7 +1366,8 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
existing column, if the <literal>USING</literal> clause does not change
the column contents and the old type is either binary coercible to the new
type or an unconstrained domain over the new type, a table rewrite is not
- needed; but any indexes on the affected columns must still be rebuilt.
+ needed; however, indexes will still have to be rebuilt unless the system
+ can verify that sort order and/or hashing semantics are unchanged.
Table and/or index rebuilds may take a
significant amount of time for a large table; and will temporarily require
as much as double the disk space.
--
2.20.1