]> granicus.if.org Git - postgresql/commit
Fix problem in which sloppily-coded test in ExecInitIndexScan would
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 23 May 2000 16:56:37 +0000 (16:56 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 23 May 2000 16:56:37 +0000 (16:56 +0000)
commit1c5b902018bc3b045e933817603ccdb7c0205c48
tree73bb2303dfe593baa59cb107e3a435d4f7add3a6
parent1c8244ec678dc4c2dffdcffd5cb51c04e9fc5dfc
Fix problem in which sloppily-coded test in ExecInitIndexScan would
think that both sides of indexqual look like index keys.  An example is
create table inside (f1 float8 primary key);
create table outside (g1 float8, g2 float8);
select * from inside,outside where f1 = atan2(g1+1, g2);
ERROR:  ExecInitIndexScan: both left and right ops are rel-vars
(note that failure is potentially platform-dependent).  Solution is a
cleanup I had had in mind to make anyway: functional index keys should
be represented as Var nodes in the fixed indexqual, just like regular
index keys.
src/backend/executor/nodeIndexscan.c
src/backend/optimizer/plan/createplan.c