| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | 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 17:49:19 |
| Message-ID: | 200310201849.19668.dev@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Monday 20 October 2003 18:24, Joe Conway wrote:
> Richard Huxton wrote:
> > So - gain by not re-planning on every call, but maybe lose because your
> > plan is not so precise.
> >
> > Of course, any queries you build dynamically and run via EXECUTE will
> > have to be planned each time.
>
> This question gets even more complex in 7.4, where many simple SQL
> functions will get inlined, and library preloading is available to speed
> that first PL/pgSQL call.
What will be the effects of inlining? Does it mean the planner merges the
function's plan into the larger query?
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-10-20 17:53:42 | [postgres] Deutsche PostgreSQL-Mailingliste unter postgresql.org |
| Previous Message | Joe Conway | 2003-10-20 17:24:19 | Re: Which is faster SQL or PL/PGSQL |