aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-01-15 14:09:35 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-01-15 14:09:35 -0500
commit0777f7a2e8e0a51f0f60cfe164d538bb459bf9f2 (patch)
tree8fb8890cc978833ede6572949b5558b125e2361f /src/backend/access/gist/gist.c
parent83f2061dd037477ec8479ee160367840e203a722 (diff)
downloadpostgresql-0777f7a2e8e0a51f0f60cfe164d538bb459bf9f2.tar.gz
postgresql-0777f7a2e8e0a51f0f60cfe164d538bb459bf9f2.zip
Fix matching of boolean index columns to sort ordering.
Normally, if we have a WHERE clause like "indexcol = constant", the planner will figure out that that index column can be ignored when determining whether the index has a desired sort ordering. But this failed to work for boolean index columns, because a condition like "boolcol = true" is canonicalized to just "boolcol" which does not give rise to an EquivalenceClass. Add a check to allow the same type of deduction to be made in this case too. Per a complaint from Dima Pavlov. Arguably this is a bug, but given the limited impact and the small number of complaints so far, I won't risk destabilizing plans in stable branches by back-patching. Patch by me, reviewed by Michael Paquier Discussion: https://postgr.es/m/1788.1481605684@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions