| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
| Cc: | <hs(at)cybertec(dot)at>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PREPARE / EXECUTE |
| Date: | 2002-10-23 21:35:49 |
| Message-ID: | 87n0p4ltxm.fsf@mailbox.samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
> The standard approach to such a scenario would imho be to write
> stored procedures for the complex queries (e.g. plpgsql) and use
> that from the client. Maybe even eliminate a few ping pongs between
> client and server.
Since PL/PgSQL cached query plans are flushed when the backend exits,
how would this help?
Regarding the original suggestion of storing prepared plans on disk, I
agree with Tom -- it's basically the same idea as storing plans in
shared memory, which we previously considered (and Karel implemented),
but ultimately decided to remove. IMHO, the utility of this feature
doesn't justify the problems that would come with implementing it (see
the archives for the original implementation discussions).
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-10-23 21:50:34 | Re: pg_dump and large files - is this a problem? |
| Previous Message | Hans-Jürgen Schönig | 2002-10-23 19:09:45 | Re: PREPARE / EXECUTE |