| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | josh(at)agliodbs(dot)com, Richard Huxton <dev(at)archonet(dot)com>, Michael Pohl <pgsql(at)newtopia(dot)com>, pgsql-sql(at)postgresql(dot)org, "George A(dot)J" <jinujosein(at)yahoo(dot)com> |
| Subject: | Re: Which is faster SQL or PL/PGSQL |
| Date: | 2003-10-20 19:50:00 |
| Message-ID: | 13678.1066679400@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Joe Conway <mail(at)joeconway(dot)com> writes:
> Josh Berkus wrote:
>> While we're on the topic, anyone know any good ways to speed up EXECUTE
>> statements in PL/pgSQL functions?
> Never tried it, but is it possible to use a prepared statement inside a
> PL/pgSQL function?
You could probably EXECUTE prepare and execute statements, but I don't
see the point --- this would just be an extremely tedious way of
duplicating plpgsql's normal query-plan-caching behavior.
AFAICS, the whole point of EXECUTE in plpgsql is that it doesn't take
any shortcuts, and so the answer to Josh's question can only be "don't
use EXECUTE"...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2003-10-20 19:51:42 | Re: Crosstab question |
| Previous Message | weigelt | 2003-10-20 19:05:31 | Re: [postgres] Deutsche PostgreSQL-Mailingliste unter postgresql.org |