Re: avoid select expens_expr(col) like unneccessary calculations

On 8 Jul 2003, Markus Bertheau wrote:

> when you have
> select expensive_expression(column), * from table offset 20 limit 40
>
> can you somehow save the cost for the first 20 calculations of
> expensive_expression?

Right now the only way I can think of that might work is to push the
offset/limit into a subselect on table and then do the
expensive_expression at the top level.


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match