Well I'm curious are you using monitoring? I never tested the updated jdbc driver with monitoring enabled until I upgraded to 1.8 On Dec 12, 2012 2:30 PM, "Jonathan Scott" <[email protected]> wrote:
> On Wed, Dec 12, 2012 at 12:32 PM, Paul Robert Marino > <[email protected]>wrote: > >> I was the first one to point out the jdbc driver >> it does help significantly but i never could find any thing in the >> change log to explain why it fixes the issue >> its not a 100% fix but you will notice a 95% reduction in idle >> connections and it will be relatively stable give or take 5 idle >> connections. >> >> > I remember you doing so, and I was one of the ones who started testing as > soon as you posted. Unfortunately, it didn't do anything to help in my > situation as far as I could tell (perhaps slowing down but never reducing). > I still had stacking idle transactions necessitating nightly restarts. My > idle transaction count would quadruple every few hours until postgresql > stopped accepting connections. Adjusting the connection count only delayed > the inevitable. > > Applying the patch to python-psycopg2 is the only thing that has thus far > proven to provide an actual fix to my issues. I have been running solid for > days, never breaking more than 10 idle transactions (consistently running > around 3-4), and not needing a full application recycle (and ipcs flush of > apache processes) yet. > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
