From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | wsheldah(at)lexmark(dot)com |
Subject: | Re: functions vs embedded SQL |
Date: | 2001-11-07 16:34:27 |
Message-ID: | 4.2.0.58.20011107172703.00a72550@pop.freesurf.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2001-11-07 16:50:32 | Re: [pgadmin-hackers] Fwd: Re: Howto change column |
Previous Message | Gordan Bobic | 2001-11-07 16:22:48 | More Performance Questions |