I've noticed that if a client uses PQexecParams, the query plan
appears to be identical to the plan chosen for PQprepare/PQexecPrepared,
which might not be as optimal as a plan chosen for PQexec. I can
understand the PQprepare case since the planner doesn't know what
parameters will actually be
Michael Fuhr [EMAIL PROTECTED] writes:
I've noticed that if a client uses PQexecParams, the query plan
appears to be identical to the plan chosen for PQprepare/PQexecPrepared,
which might not be as optimal as a plan chosen for PQexec. I can
understand the PQprepare case since the planner
On Sun, Nov 20, 2005 at 05:21:03PM -0500, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
Is PQexecParams just shorthand for a prepare followed by an execute?
Yes, but it uses the unnamed statement, so in recent server versions you
should get a postponed plan that uses the Bind
Michael Fuhr [EMAIL PROTECTED] writes:
Here's a simplified client program (the original has
error checking but I've stripped it out for brevity; this simplified
version behaves the same way):
I get the same results for all three after fixing the subscripting
mistake:
- values[1] =
On Sun, Nov 20, 2005 at 08:34:39PM -0500, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
Here's a simplified client program (the original has
error checking but I've stripped it out for brevity; this simplified
version behaves the same way):
I get the same results for all three
