On 04/06/2009, Kenneth Cox <[email protected]> wrote: > On Tue, 02 Jun 2009 09:33:16 -0400, sebb <[email protected]> wrote: > > > If you are sure that this is a regression - i.e. the identical JMX > > file works in 2.3.2 but does not work in 2.3.3 - then please file a > > Bugzilla issue (see website for details) with full details, and attach > > the following: > > > > I verified that the identical JMX file works in 2.3.2 but not in 2.3.3. I > created bug 47313 for this issue. Setting Max Number of Connections to 0 > did not fix it for 2.3.3.
There were quite a few changes between 2.3.2 and 2.3.3, and I overlooked a single line ... this turns out to be the problem. The code was updated to ensure that all the statements were properly closed - unfortunately this includes the prepared statement. So I'm afraid 2.3.3 won't work with prepared statements. > The funny thing is that 2.3.2 worked, but not > exactly as I expected. I have 2 threads (in a connection pool with max 2 > connections) running 2 iterations, and in the postgres syslog output I saw 4 > sequences of parse/bind/execute. I was expecting to see the "parse" step > omitted on the 2nd and subsequent iterations for each thread, e.g. > parse/bind/execute/bind/execute. Using a connection pool count > 0 is not recommended, as the connections aren't tied to particular threads. See if the same happens with max=0, which ensures a single connection per thread. > Regards, > Ken > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [email protected] > For additional commands, e-mail: > [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
