Prints a progress report as each index is reindexed. Specifies that indexes will be rebuilt on a new tablespace. There are several caveats to be aware of when using this option - see Rebuilding Indexes Concurrently below.įor temporary tables, REINDEX is always non-concurrent, as no other session can access them, and non-concurrent reindex is cheaper. When this option is used, PostgreSQL will rebuild the index without taking any locks that prevent concurrent inserts, updates, or deletes on the table whereas a standard index rebuild locks out writes (but not reads) on the table until it's done. Presently, REINDEX DATABASE and REINDEX SYSTEM can only reindex the current database, so their parameter must match the current database's name. Index and table names can be schema-qualified. The name of the specific index, table, or database to be reindexed. This form of REINDEX cannot be executed inside a transaction block. Indexes on user tables are not processed. Indexes on shared system catalogs are included. Recreate all indexes on system catalogs within the current database. Indexes on shared system catalogs are also processed. Recreate all indexes within the current database. If a table of this schema has a secondary “ TOAST” table, that is reindexed as well. Recreate all indexes of the specified schema. This form of REINDEX cannot be executed inside a transaction block when used with a partitioned table. If the table has a secondary “ TOAST” table, that is reindexed as well. Recreate all indexes of the specified table. This form of REINDEX cannot be executed inside a transaction block when used with a partitioned index.
0 Comments
Leave a Reply. |