Re: JDBC, prepared queries, and partitioning
От | Kris Jurka |
---|---|
Тема | Re: JDBC, prepared queries, and partitioning |
Дата | |
Msg-id | Pine.BSO.4.64.0802131537500.26092@leary.csoft.net обсуждение исходный текст |
Ответ на | Re: JDBC, prepared queries, and partitioning (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: JDBC, prepared queries, and partitioning
|
Список | pgsql-jdbc |
On Wed, 13 Feb 2008, Simon Riggs wrote: > On Wed, 2008-02-13 at 13:51 -0500, Kris Jurka wrote: >> >> Using protocol version 2 will not prepare queries so constraint exclusion >> can be used. Just append protocolVersion=2 to your URL. > > What about the prepare threshold? > I'm not sure what your question is, you might be asking: 1) Do I need to be aware of prepare threshold with V2 connections? No, prepareThreshold only affects V3 protocol connections. Prior to the 8.0 release there was rudimentary support for converting PreparedStatements to SQL level PREPARE/EXECUTE that worked with V2, but that was ripped out in the major 8.0 rewrite and V2 always interpolates parameters into the query and executes it directly. 2) Can't I use prepare threshold with V3 instead of switching to V2 and achieve the same effect? No, in V3 all prepared statements are prepared regardless of the threshold. The difference is in the level of "preparedness" by using either a named or unnamed statement at the protocol level. See my previous email for more details on that topic. Kris Jurka
В списке pgsql-jdbc по дате отправления: