diff options
author | Michael Paquier <michael@paquier.xyz> | 2021-02-04 14:34:20 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2021-02-04 14:34:20 +0900 |
commit | c5b286047cd698021e57a527215b48865fd4ad4e (patch) | |
tree | f6be35e4e5f3375949226731d3ce682398bd6c39 /src/backend/access/gist/gistutil.c | |
parent | 9624321ec502f4e4f4722290b358694049447f95 (diff) | |
download | postgresql-c5b286047cd698021e57a527215b48865fd4ad4e.tar.gz |
Add TABLESPACE option to REINDEX
This patch adds the possibility to move indexes to a new tablespace
while rebuilding them. Both the concurrent and the non-concurrent cases
are supported, and the following set of restrictions apply:
- When using TABLESPACE with a REINDEX command that targets a
partitioned table or index, all the indexes of the leaf partitions are
moved to the new tablespace. The tablespace references of the non-leaf,
partitioned tables in pg_class.reltablespace are not changed. This
requires an extra ALTER TABLE SET TABLESPACE.
- Any index on a toast table rebuilt as part of a parent table is kept
in its original tablespace.
- The operation is forbidden on system catalogs, including trying to
directly move a toast relation with REINDEX. This results in an error
if doing REINDEX on a single object. REINDEX SCHEMA, DATABASE and
SYSTEM skip system relations when TABLESPACE is used.
Author: Alexey Kondratov, Michael Paquier, Justin Pryzby
Reviewed-by: Álvaro Herrera, Michael Paquier
Discussion: https://postgr.es/m/8a8f5f73-00d3-55f8-7583-1375ca8f6a91@postgrespro.ru
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions