mirror of
https://github.com/postgres/postgres.git
synced 2026-10-23 13:29:09 +03:00
a846ee9854
bt_child_highkey_check() walks right along the child level following btpo_next links, reading a page on each iteration, but its loop lacked a CHECK_FOR_INTERRUPTS(). Every other page-traversal loop in verify_nbtree.c already has one. The loop's existing checks do not guarantee a timely exit on a corrupt index. The in-loop cycle check only fires when a rightlink points back through the block the walk started from, or to a page whose btpo_prev points to itself, so a cycle further downstream can go undetected -- for example a run of pages all flagged P_INCOMPLETE_SPLIT, which skips both the high-key comparison and bt_downlink_missing_check() and so never reaches an error. Such an index, or simply a very long rightlink chain, makes the walk effectively uninterruptible. Since amcheck exists to be run against possibly-corrupt indexes, make this walk respond to query cancellation and shutdown requests like the sibling loops do. Author: Paul Kim <mok03127@gmail.com> Reviewed-by: shihao zhong <zhong950419@gmail.com> Discussion: https://www.postgresql.org/message-id/20260717151437.10713-1-mok03127@gmail.com
The PostgreSQL contrib tree
---------------------------
This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree. This does not preclude their
usefulness.
User documentation for each module appears in the main SGML
documentation.
When building from the source distribution, these modules are not
built automatically, unless you build the "world" target. You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.
Some directories supply new user-defined functions, operators, or
types. To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command. In a fresh database,
you can simply do
CREATE EXTENSION module_name;
See the PostgreSQL documentation for more information about this
procedure.