| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Jingren Zhou <jrzhoupro(at)hotmail(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PREPARE/EXECUTE across backends? |
| Date: | 2003-10-02 02:10:23 |
| Message-ID: | Pine.LNX.4.33.0310012209040.814-100000@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 1 Oct 2003, Jingren Zhou wrote:
> Hi,
>
> >From the document, it seems that PREPARE/EXECUTE works only in the same
> session. I am wondering whether postgres can prepare a query (save the plan)
> for difference backends.
>
> I am working on a project which requires executing "psql -c 'query'" in
> command line multiple times. Since the performance is critical, it would be
> nice to prepare the same query first to avoid being parsed/optimized each
> time. But psql opens a new backend each time, it looks like that
> PREPARE/EXECUTE doesn't work. Is there any workaround?
Your real overhead here isn't from having to prepare the query each time,
it's from having to start psql and open a new connection each time.
Perhaps you need to rethink your design and go with something that will
maintain a persistent connection.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-02 02:43:46 | Re: PREPARE/EXECUTE across backends? |
| Previous Message | Christopher Kings-Lynne | 2003-10-02 01:44:49 | Re: NOTICE: CREATE TABLE will create implicit triggers |