Re: BUG #14107: Major query planner bug regarding subqueries and indices

> Seems like it. I've asked folks on IRC for help, and it was confirmed the
> bug exists since 8.2


So, as it currently stands, queries of the following synopsis are de
facto unusable with PostgreSQL, as these will always ignore any existing
indices and trigger a full table scan instead:


SELECT ... FROM a WHERE a.x = ? OR a.y IN (...);

SELECT ... FROM a JOIN b ON (...) WHERE a.x = ? OR b.y = ?;


The following SQL fiddle demonstrates the bug:
http://sqlfiddle.com/#!15/ab714/2

Does anybody care? Shouldn't something like this be fixed ASAP??