Re: [PERFORM] Bad Execution Plan with "OR" Clauses Across Outer-Joined Tables

e has "exists" in both HQL and criteria API > (e.g. see > http://www.cereslogic.com/pages/2008/09/22/hibernate-criteria-subqueries-exists/ > for > criteria). So, may be it's easier for you to tune your hibernate query to > use exists > > > 2013/4/30 Mark Hamp

[PERFORM] Bad Execution Plan with "OR" Clauses Across Outer-Joined Tables

I have a Hibernate-generated query (That's not going to change, so let's just focus on the Postgres side for now) like this: SELECT * from PERSON p where p.PERSON_ID in ( select distinct p2.PERSON_ID from PERSON p2 left oute