Re: for/loop performance in plpgsql ?

Federico <fepede(at)inwind(dot)it> writes:
>> Well - the query might well be pre-parsed which means it wouldn't notice any
>> updated stats. Can you provide an example of your code?

> It's nothing particular strange. It's something like :

> result record;

> for result in select rai, tem
> from data
> where (codice LIKE cod_staz and
> ora > orain and
> ora <= orafin) loop

Which of these names are columns of the selected tables, and which ones
are plpgsql variables?

The planner has to fall back to default selectivity estimates when it's
looking at queries involving plpgsql variables (since it can't know
their actual values in advance). I suspect your problem is related to
an inaccurate default estimate.

regards, tom lane