Re: Strange RETURN NEXT behaviour in Postgres 8.0

"Sergey E. Koposov" <math@sai.msu.ru> writes:
> LOOP
>         FETCH cur into rec;
>         RETURN NEXT rec;
>         EXIT WHEN NOT FOUND;
> END LOOP;
> RETURN;

Don't you think you should have the EXIT *above* the RETURN NEXT?
I would expect this to emit a bogus row of nulls after the last row
returned by the cursor.  (At least that's what I get with current
sources.  Pre-8.0 it might return the last row twice.)

Running it on a 500-million-row table would quite possibly run out of
memory or disk space, too, because RETURN NEXT accumulates all the
results before the function is actually exited.
        regards, tom lane