From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
To: | 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-12 23:06:58 |
Message-ID: | Pine.LNX.4.21.0308130900460.18571-100000@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 12 Aug 2003, Tom Lane wrote:
> 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?
Can you give an example of this usage of this API? I am wondering whether
releasing this specific feature would be eclipsed by a generalised bound
variables solution in a future release... still, that's a nice speed up
:-).
Thanks,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-12 23:12:09 | Re: Parsing speed (was Re: pgstats_initstats() cost) |
Previous Message | Tom Lane | 2003-08-12 22:57:39 | Re: Proper Unicode support |