From 18657a960e125336f704ea058e25c27bd3900dcb Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 5 May 2024 19:28:19 +0200 Subject: Adding upstream version 3.40.1. Signed-off-by: Daniel Baumann --- www/lang_reindex.html | 204 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 204 insertions(+) create mode 100644 www/lang_reindex.html (limited to 'www/lang_reindex.html') diff --git a/www/lang_reindex.html b/www/lang_reindex.html new file mode 100644 index 0000000..9cc4713 --- /dev/null +++ b/www/lang_reindex.html @@ -0,0 +1,204 @@ + + + + + +REINDEX + + + +
+ + + +
+
+Small. Fast. Reliable.
Choose any three. +
+
+ +
+ +
+
+ + + +
+
+
+ +
+
+
+REINDEX +
+
+ + + + +

reindex-stmt: +

+
+
+ + + + +REINDEX + + + +schema-name + + + +. + + + + + +index-name + + + + + + + + +table-name + + + + + + + + + +collation-name + + + + + + + +
+
+ + +

The REINDEX command is used to delete and recreate indices from scratch. +This is useful when the definition of a collation sequence has changed, or +when there are indexes on expressions involving a function whose definition +has changed. +

+ +

If the REINDEX keyword is not followed by a collation-sequence or database +object identifier, then all indices in all attached databases are rebuilt. + +

If the REINDEX keyword is followed by a collation-sequence name, then +all indices in all attached databases that use the named collation sequences +are recreated. + +

Or, if the argument attached to the REINDEX identifies a specific +database table, then all indices attached to the database table are rebuilt. +If it identifies a specific database index, then just that index is recreated. + +

For a command of the form "REINDEX name", a match +against collation-name takes precedence over a match +against index-name or table-name. +This ambiguity in the syntax may be avoided by always specifying a +schema-name when reindexing a specific table or index. +

This page last modified on 2020-04-29 04:02:25 UTC

+ -- cgit v1.2.3