"Harry Rossignol" <[EMAIL PROTECTED]> writes:
> My experience using PQexecParams is that it has a performance
> degradation of a factor of 100's if not thousands.
This is demonstrably not so in general. You may be hitting a case where
the planner chooses a poor plan for lack of information about
My experience using PQexecParams is
that it has a performance degradation of a factor of 100’s if not
thousands.
I have reworked my queries to DECLARE a binary cursor for
the return results and using a fixed text statement for the PQexec
select.
It doesn’t help on Inserts and Updates but
Tony wrote:
> CREATE OR REPLACE FUNCTION f_multiparam (
> i1 integer,
> i2 varchar,
> OUT o1 varchar
> ) AS
> $$
> BEGIN
> o1 := 'i2 was ' || i2;
> END;
> $$
> LANGUAGE plpgsql;
>
> CREATE OR REPLACE FUNCTION f_showperformstatus () RETURNS varchar AS
> $$
> DECLARE
> outparameter varcha
"Tony" <[EMAIL PROTECTED]> writes:
> Defined a function with OUT paramter. Attempts to call it fail as the
> function can not be found.
Apparently, you don't understand how OUT parameters work either :-(
Perhaps the examples here will help:
http://www.postgresql.org/docs/8.1/static/xfunc-sql.html
"Tony S" <[EMAIL PROTECTED]> writes:
> Function defined with INOUT parameter. Value of parameter is not returned
> to calling function.
You are confused about the meaning and use of INOUT. It's not some kind
of pass-by-reference parameter, it's just a shorthand for separate IN
and OUT parameters
The following bug has been logged online:
Bug reference: 2108
Logged by: Tony
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Debian 1:3.3.5-8ubuntu2, 2.6.10-5-k7, i686
Description:Function with OUT parameters not recognized, using
plpgsql
The following bug has been logged online:
Bug reference: 2107
Logged by: Tony S
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Debian 1:3.3.5-8ubuntu2, 2.6.10-5-k7, i686
Description:Function INOUT parameter not returned to caller, causes
