SEO

#1 (**permalink**) 04-10-2008, 09:34 AM

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 it sure helps on straight
select statement queries.

#2 (**permalink**) 04-10-2008, 09:34 AM

"Harry Rossignol" <harrywr2@comcast.net> 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 the value
of a parameter ... but with no details about the query or even mention
of which PG version you're talking about, this bug report isn't worth
the electrons it's written on.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

PQexecParams performance