At 17:05 06/11/01 -0500, you wrote:
>I'm pretty sure that Postgresql does NOT save the query plan with stored
>procedures or views, so there's no performance gain from that. There is also
>never a performance loss from running a stored procedure with a query plan
>that's no longer optimal, as sometimes happens with MS SQL Server. (Or
>used to
>as of version 7.0 anyway...) Any performance gains from stored procedures in
>Postgresql would come from making fewer trips between the server and
>client, and
>from anything done in them that happens to run faster than it would on the
>client. There are also other more general reasons to use stored procs,
>but you
>seem to be familiar with them. HTH,
Optimization can only be achieved at database design level.
Most databases need to be re-designed to benefit from triggers, PL/pgSQL
and cron jobs.
/JMP
