Re: JDBC, prepared queries, and partitioning
От
Kris Jurka
Тема
Re: JDBC, prepared queries, and partitioning
Дата
Msg-id
Pine.BSO.4.64.0802131348050.27322@leary.csoft.net
Ответ на
JDBC, prepared queries, and partitioning (Josh Berkus)
Список
Дерево обсуждения
JDBC, prepared queries, and partitioning Josh Berkus <josh@agliodbs.com>
Re: JDBC, prepared queries, and partitioning Kris Jurka <books@ejurka.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Tom Lane <tgl@sss.pgh.pa.us>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning "Stephen Denne" <Stephen.Denne@datamail.co.nz>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Josh Berkus <josh@agliodbs.com>
Re: JDBC, prepared queries, and partitioning Oliver Jowett <oliver@opencloud.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Oliver Jowett <oliver@opencloud.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Oliver Jowett <oliver@opencloud.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Oliver Jowett <oliver@opencloud.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Oliver Jowett <oliver@opencloud.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Oliver Jowett <oliver@opencloud.com>
Re: JDBC, prepared queries, and partitioning Tom Lane <tgl@sss.pgh.pa.us>
Re: JDBC, prepared queries, and partitioning Oliver Jowett <oliver@opencloud.com>
Re: JDBC, prepared queries, and partitioning "Stephen Denne" <Stephen.Denne@datamail.co.nz>
Re: JDBC, prepared queries, and partitioning "Stephen Denne" <Stephen.Denne@datamail.co.nz>
Re: JDBC, prepared queries, and partitioning "Stephen Denne" <Stephen.Denne@datamail.co.nz>
Re: JDBC, prepared queries, and partitioning Kris Jurka <books@ejurka.com>
Re: JDBC, prepared queries, and partitioning "Guillaume Smet" <guillaume.smet@gmail.com>
Re: JDBC, prepared queries, and partitioning "Stephen Denne" <Stephen.Denne@datamail.co.nz>
Re: JDBC, prepared queries, and partitioning Tom Lane <tgl@sss.pgh.pa.us>
Re: JDBC, prepared queries, and partitioning "Stephen Denne" <Stephen.Denne@datamail.co.nz>
Re: JDBC, prepared queries, and partitioning Kris Jurka <books@ejurka.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Kris Jurka <books@ejurka.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Kris Jurka <books@ejurka.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Kris Jurka <books@ejurka.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Oliver Jowett <oliver@opencloud.com>
Re: JDBC, prepared queries, and partitioning Kris Jurka <books@ejurka.com>
Re: JDBC, prepared queries, and partitioning Simon Riggs <simon@2ndquadrant.com>
Re: JDBC, prepared queries, and partitioning Kris Jurka <books@ejurka.com>
On Wed, 13 Feb 2008, Josh Berkus wrote: > Since JDBC always prepares and plan-caches queries, it makes it hard to use > partitioning with a database connected to a JDBC connection pool; successive > queries in the same session will select the wrong partition, or scan the > whole partition set. > It will never scan the wrong partition. It will always scan all partitions. The server is smart enough to not generate a plan that is not valid for only one parameter set. Using protocol version 2 will not prepare queries so constraint exclusion can be used. Just append protocolVersion=2 to your URL. Kris Jurka
В списке pgsql-jdbc по дате отправления