On Wed, Jul 25, 2012 at 3:45 PM, Merlin Moncure <mmoncure@xxxxxxxxx> wrote: > On Tue, Jul 24, 2012 at 10:50 AM, Maciek Sakrejda <m.sakrejda@xxxxxxxxx> wrote: >> This may be another issue of the problem discussed here: >> http://postgresql.1045698.n5.nabble.com/avoid-prepared-statements-on-complex-queries-td4996363.html >> (Kris Jurka explains the crux of it in that thread). >> >> Note that it seems the preparing/planning interaction was not the >> poster's actual problem, but it may have been yours. As Tom Lane notes >> in that thread, this should get better in 9.2. > > jdbc should get some blame too -- it's really aggressive about > preparing queries. > indeed! Is there any reason for that? -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
