R-tree index and logging
The R-tree secondary access method uses the extensible log manager of the HCL Informix® database server to perform logical logging of its operations. These logical-log records can be used to recover an R-tree index after a database server failure or to abort the R-tree operations after a rollback.
The R-tree secondary access method creates its own logical-log
records for only some of the R-tree index operations, in particular:
- Insertion of an item into a leaf page
- Deletion of an item from a leaf page
The R-tree secondary access method does not create its own logical-log
records for the following operations; instead, the access method allows
the extensible log manager to create the logical-log records:
- Insertion of an item into or deletion from an internal branch page
- Creation of a new page due to split of a page
- Update of the bounding box or other metadata in a page
- Update of the child page of an internal branch page
- Update of the root page number in the root page when a new root page is created
The following R-tree operations are not logged at all:
- CREATE INDEX statement to create an R-tree index
- Any operation on an R-tree index of a temporary table