mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-23 05:50:40 +02:00
per-column options for btree indexes. The planner's support for this is still pretty rudimentary; it does not yet know how to plan mergejoins with nondefault ordering options. The documentation is pretty rudimentary, too. I'll work on improving that stuff later. Note incompatible change from prior behavior: ORDER BY ... USING will now be rejected if the operator is not a less-than or greater-than member of some btree opclass. This prevents less-than-sane behavior if an operator that doesn't actually define a proper sort ordering is selected. |
||
---|---|---|
.. | ||
data | ||
expected | ||
input | ||
output | ||
sql | ||
GNUmakefile | ||
Makefile | ||
parallel_schedule | ||
pg_regress.c | ||
regress.c | ||
regressplans.sh | ||
resultmap | ||
serial_schedule |