Re: Parsing speed (was Re: pgstats_initstats() cost) - Mailing list pgsql-hackers

From Gavin Sherry
Subject Re: Parsing speed (was Re: pgstats_initstats() cost)
Date
Msg-id Pine.LNX.4.21.0308130900460.18571-100000@linuxworld.com.au
Whole thread Raw
In response to Parsing speed (was Re: pgstats_initstats() cost)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Parsing speed (was Re: pgstats_initstats() cost)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proper Unicode support
Next
From: Tom Lane
Date:
Subject: Re: Parsing speed (was Re: pgstats_initstats() cost)