mirror of
https://github.com/postgres/postgres.git
synced 2025-10-21 02:52:47 +03:00
Improve handling of dropped relations for REINDEX DATABASE/SCHEMA/SYSTEM
When multiple relations are reindexed, a scan of pg_class is done first to build the list of relations to work on. However the REINDEX logic has never checked if a relation listed still exists when beginning the work on it, causing for example sudden cache lookup failures. This commit adds safeguards against dropped relations for REINDEX, similarly to VACUUM or CLUSTER where we try to open the relation, ignoring it if it is missing. A new option is added to the REINDEX routines to control if a missed relation is OK to ignore or not. An isolation test, based on REINDEX SCHEMA, is added for the concurrent and non-concurrent cases. Author: Michael Paquier Reviewed-by: Anastasia Lubennikova Discussion: https://postgr.es/m/20200813043805.GE11663@paquier.xyz
This commit is contained in:
@@ -22,6 +22,7 @@ extern Relation table_open(Oid relationId, LOCKMODE lockmode);
|
||||
extern Relation table_openrv(const RangeVar *relation, LOCKMODE lockmode);
|
||||
extern Relation table_openrv_extended(const RangeVar *relation,
|
||||
LOCKMODE lockmode, bool missing_ok);
|
||||
extern Relation try_table_open(Oid relationId, LOCKMODE lockmode);
|
||||
extern void table_close(Relation relation, LOCKMODE lockmode);
|
||||
|
||||
#endif /* TABLE_H */
|
||||
|
Reference in New Issue
Block a user