"[email protected]" <[email protected]> writes:
> I wish there were a way to force inlining, or some other mechanism as the
> performance difference is large here. I'll be using the inlining approach
> when possible, but the SQL Function approach is simpler and will likely be
> more suitable for some developers.
I'm not sure that there's any fundamental reason why we don't inline SQL
functions containing sub-selects. It may just be not having wanted to put
any effort into the case way-back-when. Inlining happens too late to
allow a resulting WHERE EXISTS to get mutated into a semijoin, but in this
example that couldn't happen anyway, so it's not much of an objection.
regards, tom lane
--
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
