Go to file

Peter Geoghegan 5bf748b86b Enhance nbtree ScalarArrayOp execution. Commit `9e8da0f7` taught nbtree to handle ScalarArrayOpExpr quals natively. This works by pushing down the full context (the array keys) to the nbtree index AM, enabling it to execute multiple primitive index scans that the planner treats as one continuous index scan/index path. This earlier enhancement enabled nbtree ScalarArrayOp index-only scans. It also allowed scans with ScalarArrayOp quals to return ordered results (with some notable restrictions, described further down). Take this general approach a lot further: teach nbtree SAOP index scans to decide how to execute ScalarArrayOp scans (when and where to start the next primitive index scan) based on physical index characteristics. This can be far more efficient. All SAOP scans will now reliably avoid duplicative leaf page accesses (just like any other nbtree index scan). SAOP scans whose array keys are naturally clustered together now require far fewer index descents, since we'll reliably avoid starting a new primitive scan just to get to a later offset from the same leaf page. The scan's arrays now advance using binary searches for the array element that best matches the next tuple's attribute value. Required scan key arrays (i.e. arrays from scan keys that can terminate the scan) ratchet forward in lockstep with the index scan. Non-required arrays (i.e. arrays from scan keys that can only exclude non-matching tuples) "advance" without the process ever rolling over to a higher-order array. Naturally, only required SAOP scan keys trigger skipping over leaf pages (non-required arrays cannot safely end or start primitive index scans). Consequently, even index scans of a composite index with a high-order inequality scan key (which we'll mark required) and a low-order SAOP scan key (which we won't mark required) now avoid repeating leaf page accesses -- that benefit isn't limited to simpler equality-only cases. In general, all nbtree index scans now output tuples as if they were one continuous index scan -- even scans that mix a high-order inequality with lower-order SAOP equalities reliably output tuples in index order. This allows us to remove a couple of special cases that were applied when building index paths with SAOP clauses during planning. Bugfix commit `807a40c5` taught the planner to avoid generating unsafe path keys: path keys on a multicolumn index path, with a SAOP clause on any attribute beyond the first/most significant attribute. These cases are now all safe, so we go back to generating path keys without regard for the presence of SAOP clauses (just like with any other clause type). Affected queries can now exploit scan output order in all the usual ways (e.g., certain "ORDER BY ... LIMIT n" queries can now terminate early). Also undo changes from follow-up bugfix commit `a4523c5a`, which taught the planner to produce alternative index paths, with path keys, but without low-order SAOP index quals (filter quals were used instead). We'll no longer generate these alternative paths, since they can no longer offer any meaningful advantages over standard index qual paths. Affected queries thereby avoid all of the disadvantages that come from using filter quals within index scan nodes. They can avoid extra heap page accesses from using filter quals to exclude non-matching tuples (index quals will never have that problem). They can also skip over irrelevant sections of the index in more cases (though only when nbtree determines that starting another primitive scan actually makes sense). There is a theoretical risk that removing restrictions on SAOP index paths from the planner will break compatibility with amcanorder-based index AMs maintained as extensions. Such an index AM could have the same limitations around ordered SAOP scans as nbtree had up until now. Adding a pro forma incompatibility item about the issue to the Postgres 17 release notes seems like a good idea. Author: Peter Geoghegan <pg@bowt.ie> Author: Matthias van de Meent <boekewurm+postgres@gmail.com> Reviewed-By: Heikki Linnakangas <hlinnaka@iki.fi> Reviewed-By: Matthias van de Meent <boekewurm+postgres@gmail.com> Reviewed-By: Tomas Vondra <tomas.vondra@enterprisedb.com> Discussion: https://postgr.es/m/CAH2-Wz=ksvN_sjcnD1+Bt-WtifRA5ok48aDYnq3pkKhxgMQpcw@mail.gmail.com		2024-04-06 11:47:10 -04:00
config	Remove AIX support	2024-02-28 15:17:23 +04:00
contrib	Make libpqsrv_cancel's return const char , not char	2024-04-05 18:23:10 +02:00
doc	Enhance nbtree ScalarArrayOp execution.	2024-04-06 11:47:10 -04:00
src	Enhance nbtree ScalarArrayOp execution.	2024-04-06 11:47:10 -04:00
.cirrus.star	Remove duplicate words in docs and code comments.	2023-10-09 09:18:47 +05:30
.cirrus.tasks.yml	ci: macos: Choose python version	2024-03-25 16:39:08 -07:00
.cirrus.yml	ci: Make compute resources for CI configurable	2023-08-23 15:15:28 -07:00
.dir-locals.el	Make Emacs perl-mode indent more like perltidy.	2019-01-13 11:32:31 -08:00
.editorconfig	Add .editorconfig	2019-12-18 09:13:13 +01:00
.git-blame-ignore-revs	Add commit `64e401b62b` to .git-blame-ignore-revs.	2024-03-26 15:08:47 -05:00
.gitattributes	Remove non-existing file from .gitattributes	2024-02-16 11:39:09 +01:00
.gitignore	Update top-level .gitignore.	2022-12-04 15:23:00 -05:00
COPYRIGHT	Update copyright for 2024	2024-01-03 20:49:05 -05:00
GNUmakefile.in	make dist uses git archive	2024-03-25 06:29:53 +01:00
HISTORY	Canonicalize some URLs	2020-02-10 20:47:50 +01:00
Makefile	Remove AIX support	2024-02-28 15:17:23 +04:00
README.md	Revise the style of a paragraph in README.md.	2024-03-21 10:16:41 -05:00
aclocal.m4	autoconf: Move export_dynamic determination to configure	2022-12-06 18:55:28 -08:00
configure	Add --copy-file-range option to pg_upgrade.	2024-03-06 12:01:01 +13:00
configure.ac	Add --copy-file-range option to pg_upgrade.	2024-03-06 12:01:01 +13:00
meson.build	Silence meson warning	2024-04-04 11:22:07 +02:00
meson_options.txt	Add backend support for injection points	2024-01-22 10:15:50 +09:00

README.md

PostgreSQL Database Management System

This directory contains the source code distribution of the PostgreSQL database management system.

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions. This distribution also contains C language bindings.

General documentation about this version of PostgreSQL can be found at https://www.postgresql.org/docs/devel/. In particular, information about building PostgreSQL from the source code can be found at https://www.postgresql.org/docs/devel/installation.html.

The latest version of this software, and related software, may be obtained at https://www.postgresql.org/download/. For more information look at our web site located at https://www.postgresql.org/.