Re: Released updated Tcl interfaces: pgin.tcl-2.1.0, - Mailing list pgsql-interfaces

From Tom Lane
Subject Re: Released updated Tcl interfaces: pgin.tcl-2.1.0,
Date
Msg-id 24110.1087945736@sss.pgh.pa.us
Whole thread Raw
In response to Re: Released updated Tcl interfaces: pgin.tcl-2.1.0,  ("Nigel J. Andrews" <nandrews@investsystems.co.uk>)
Responses Re: Released updated Tcl interfaces: pgin.tcl-2.1.0,  ("Nigel J. Andrews" <nandrews@investsystems.co.uk>)
List pgsql-interfaces
"Nigel J. Andrews" <nandrews@investsystems.co.uk> writes:
> However, since making some changes to my code I've not had time to do the
> investigation so I just thought I'd ask if there's been any reports on the
> relative speed of normal sql execution against prepared statements.

You can lose if the prepared statements are parameterized in such a way
that the planner can't see critical information.  This has been hashed
over many a time in the pgsql-performance archives (though mostly in the
context of queries in plpgsql functions).  Try EXPLAIN EXECUTE and see
if you get a materially different plan than with the straight query.
        regards, tom lane


pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: Borland PQexec error in Windows XP
Next
From: L J Bayuk
Date:
Subject: Re: Borland PQexec error in Windows XP