| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Gavin Sherry" <swm(at)linuxworld(dot)com(dot)au>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parsing speed (was Re: pgstats_initstats() cost) |
| Date: | 2003-08-13 01:45:10 |
| Message-ID: | 1d8301c3613c$8a636e50$2800a8c0@mars |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> This leaves us with a bit of a problem, though, because there isn't any
> libpq API that allows access to this speedup. I put in a routine to
> support Parse/Bind/Execute so that people could use out-of-line
> parameters for safety reasons --- but there's no function to do
> Bind/Execute against a pre-existing prepared statement. (I had to make
> a hacked version of libpq to do the above testing.)
>
> I'm beginning to think that was a serious omission. I'm tempted to fix
> it, even though we're past feature freeze for 7.4. Comments?
I say fix it...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-08-13 01:50:40 | Re: Parsing speed (was Re: pgstats_initstats() cost) |
| Previous Message | Bruce Momjian | 2003-08-13 00:53:17 | Re: TODO items |