aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2006-01-29 17:27:42 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2006-01-29 17:27:42 +0000
commita1b7e70c5fbcb52ee5fb16ef567365a978c6fea7 (patch)
tree20091165257468f28e42ca107a094b8307da0a78 /src/backend/access/gist/gistvacuum.c
parent4400ca2bada53fedda1c6ac10b3eaacb82e1b33b (diff)
downloadpostgresql-a1b7e70c5fbcb52ee5fb16ef567365a978c6fea7.tar.gz
postgresql-a1b7e70c5fbcb52ee5fb16ef567365a978c6fea7.zip
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.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions