[pgpool-general: 1339] Re: Java usage of pgpool 2
matt.sell at fluke.com
Thu Jan 24 02:42:16 JST 2013
We are within a couple of weeks of switching our production Glassfish 18.104.22.168-based environment to PGPool. We've been testing against PGPool 3.2.1 for about a month now with no observed problems.
We *did* have problems where PGPool 3.2.0 was crashing when using the "ping" command from Glassfish to test the connection, and again when retrieving large objects (byte arrays) from PG via PGPool. Those problems have been fixed (at least as far as our use case goes) as of 3.2.1. The in-memory query cache feature was a welcome addition and gives us a little performance boost.
With the exception of the large object composed using a byte array, our usage of PG via PGPool is pretty simplistic, though. We're comfortable moving forward with PGPool 3.2.1 and PG 9.2.
From: pgpool-general-bounces at pgpool.net [mailto:pgpool-general-bounces at pgpool.net] On Behalf Of Nick Hristov
Sent: Wednesday, December 05, 2012 10:31 AM
To: pgpool-general at pgpool.net
Subject: [pgpool-general: 1237] Java usage of pgpool 2
My company is currently thinking about deploying pgpool as a high availability solution of our current postgresql installation (we want to be able to have an automated method of switching to a hot-standby pg instance at any point).
We are a java shop, and will be connecting to pg pool via the JDBC4 driver (its really jdbc3 under the covers).
The problem is that we discovered a complete show stopper bug, where pg pool crashes immediately upon connection with the JDBC driver. Connections/queries via psql work quite fine.
Upon further investigation by one of my colleagues we discovered the issue was this: http://www.pgpool.net/mantisbt/view.php?id=21 .
Even though we applied the patch, I am quite uneasy, because this is a show stopper bug, imho. I am worried that this could prove to be just the beginning of a series of issues.
My question is, does anybody have a sense how many companies/organizations have chosen to deploy a pgpool/java in their production environment? What is the overall impression of the stability of the product? Any gotchas, or clear do-not-do-this items that you can point out?
Thank you very much,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pgpool-general