Thread: pgsql: Fix code that checks to see if an index can be considered to
pgsql: Fix code that checks to see if an index can be considered to
From
tgl@postgresql.org (Tom Lane)
Date:
Log Message:
-----------
Fix code that checks to see if an index can be considered to match the query's
requested sort order. It was assuming that build_index_pathkeys always
generates a pathkey per index column, which was not true if implied equality
deduction had determined that two index columns were effectively equated to
each other. Simplest fix seems to be to install an option that causes
build_index_pathkeys to support this behavior as well as the original one.
Per report from Brian Hirt.
Tags:
----
REL8_1_STABLE
Modified Files:
--------------
pgsql/src/backend/optimizer/path:
indxpath.c (r1.191.2.4 -> r1.191.2.5)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c.diff?r1=1.191.2.4&r2=1.191.2.5)
pathkeys.c (r1.73.2.1 -> r1.73.2.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c.diff?r1=1.73.2.1&r2=1.73.2.2)
pgsql/src/include/optimizer:
paths.h (r1.88 -> r1.88.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/paths.h.diff?r1=1.88&r2=1.88.2.1)