* da...@lang.hm (da...@lang.hm) wrote:
> On Wed, 22 Apr 2009, Stephen Frost wrote:
>> Erm.. Prepared queries is about using PQexecPrepared(), not about
>> sending a text string as an SQL EXECUTE(). PQexecPrepared takes an
>> array of arguments. That gets translated into a Bind command in the
>>
* Glenn Maynard (glennfmayn...@gmail.com) wrote:
> I'd suggest this be mentioned in the sql-prepare documentation, then,
> because that documentation only discusses using prepared statements to
> eliminate redundant planning costs. (I'm sure it's mentioned in the
> API docs and elsewhere, but if i
On Tue, Apr 21, 2009 at 3:58 PM, Tom Lane wrote:
> Ah. The problem is that your view contains constants in the UNION arms:
> In 8.2 and 8.3, the planner is only smart enough to generate
> inner-indexscan nestloop plans on UNIONs if all the elements of the
> SELECT lists are simple variables (tha
"John L. Clark" writes:
> Thanks for your help, Tom. I am certainly amused and pleased that my
> exact use case is handled in the very next PostgreSQL release.
Well, sir, your timing is excellent ;-). That's been a known problem
for quite some time, and it was only in this release cycle that it
Stephen Frost wrote on 22.04.2009 23:51:
What about 4 individual prepared inserts? Just curious about it.
4 inserts, one prepared statement each (constructing the prepared
statement only once), in a single transaction: 1.68s
I'm surprised that there's any win here at all.
For a sin
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
