| From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
|---|---|
| To: | Michael Meskes <Michael(dot)Meskes(at)usa(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Postgres Speed or lack thereof |
| Date: | 1999-01-19 02:15:01 |
| Message-ID: | 36A3EAA5.B0F13B40@krs.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Meskes wrote:
>
> On Sun, Jan 17, 1999 at 07:23:15PM -0800, Tom wrote:
> > This also wouldn't you give you any benefit from "prepare" that would
> > speed up repeated executions of the same statement. PostgreSQL does allow
> > statements to be prepared right? If it doesn't, chances are COPY has a
>
> Since when? I thought we're still looking for someone to implement it, i.e.
> at least the PREPARE statement.
1. PG can handle prepared queries.
Parser & Planner can parse/plan (i.e. prepare) query with
parameters once, so such prepared query can be executed
many times by executor without parser/planner invocation.
2. We have to implement some interface to use this ability.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Taral | 1999-01-19 02:26:40 | Prepared statements (was: Postgres Speed or lack thereof) |
| Previous Message | Tom Lane | 1999-01-19 02:03:08 | Re: [HACKERS] Postgres Speed or lack thereof |