Re: storing intermediate results in recursive plpgsql functions

>>(apprently sql functions do not automatically end
>>transactions/release locks like plpgsql functions do)
>>
>
> Say what?  There's no difference on that score for any kind of function;
> none of them end transactions or release locks at exit.


If that's the case, then this is the second time in a week I've found
huge errors in this darn PostgreSQL Developer's Handbook I bought.  I'm
coming very close to tossing this thing in the garbage.

"When a PL/pgSQL function locks a table, the lock is released when the
PL/pgSQL function returns".

"You can't have transactions in PL/pgSQL functions.  Every function is
executed in one transaction."

This book is really starting to tick me off.  Grr.  I'm amazed that
there are errors of this magnitude.  The authors are Ewald Geschwinde
and Hans-Jurgen Schonig, does anyone know their credentials?

Thanks for clearing that up, Tom.

-Fran