| From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
|---|---|
| To: | Peter T Mount <psqlhack(at)maidast(dot)demon(dot)co(dot)uk> |
| Cc: | ocie(at)paracel(dot)com, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Speedups |
| Date: | 1998-03-05 02:29:39 |
| Message-ID: | 34FE0E13.6DBC7B4C@sable.krasnoyarsk.su |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter T Mount wrote:
>
> On Wed, 4 Mar 1998 ocie(at)paracel(dot)com wrote:
>
> > This may sound like an obvious question, but if a user defines a
> > query, do we save the query plan? This would reduce the
> > communications between the client and server (a small gain), and allow
> > the server to start executing the query as soon as it recognized the
> > name of the stored query and parsed the arguments.
>
> Not sure ofhand, but it would be useful for JDBC's PreparedStatement and
> CallableStatement classes
We can implement it very easy, and fast. Execution plan may be reused
many times. Is this feature in standard ?
What is proposed syntax if not ?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brett McCormick | 1998-03-05 02:33:18 | Re: [HACKERS] alpha/64bit weirdness |
| Previous Message | Brett McCormick | 1998-03-05 02:28:28 | Re: [HACKERS] alpha/64bit weirdness |