Re: Some question about lazy subquery/procedures execution in SELECT ... ORDER BY... LIMIT N queries

Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> writes:
> Is here any reason why Postgresql calculates subqueries/storable procedures
> in select list before applying ORDER BY / LIMIT?

Well, that's the definition of ORDER BY --- it happens after computing
the select list, according to the SQL standard. We try to optimize this
in some cases but you can't really complain when we don't. Consider
putting the expensive function outside the ORDER BY/LIMIT, ie

select ..., expensive_fn() from (select ... order by ... limit ...) ss;

regards, tom lane