Re: [PERFORM] Query much slower when run from postgres function - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: [PERFORM] Query much slower when run from postgres function
Date
Msg-id 491f66a50903091256n7fe4a3f6i93267d0d53b983cb@mail.gmail.com
Whole thread Raw
In response to Re: [PERFORM] Query much slower when run from postgres function  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PERFORM] Query much slower when run from postgres function  (James Mansion <james@mansionfamily.plus.com>)
Re: [PERFORM] Query much slower when run from postgres function  (Oliver Jowett <oliver@opencloud.com>)
List pgsql-jdbc


On Mon, Mar 9, 2009 at 1:16 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Guillaume Smet <guillaume.smet@gmail.com> writes:
> Unnamed prepared statements are planned after binding the values,
> starting with 8.3, or more precisely starting with 8.3.2 as early 8.3
> versions were partially broken on this behalf.

No, 8.2 did it too (otherwise we wouldn't have considered 8.3.0 to be
broken...).  The thing I'm not too clear about is what "use of an
unnamed statement" translates to for a JDBC user.

Tom,

The driver will use unnamed statements for all statements until it sees the same statement N times where N is 5 I believe, after that it uses a named statement.

Dave

pgsql-jdbc by date:

Previous
From: Mario Splivalo
Date:
Subject: Re: [PERFORM] Query much slower when run from postgres function
Next
From: James Mansion
Date:
Subject: Re: [PERFORM] Query much slower when run from postgres function