On 06.11.2012 06:01, Tom Lane wrote: > Paul Robert Marino <prmari...@gmail.com> writes: >> Ive been doing some testing and I am fairly positive I found out why >> the number of connections in PostgreSQL increases and its not a >> spacewalk bug at all. >> It looks like its a JDBC bug [ and is fixed in 8.4-703 ] > > This is really interesting, but I looked through the upstream commit > logs, and I can't see any patches between 8.4-701 and 8.4-703 that look > like they'd cure a "connection leak" such as you're describing. There > are a couple of fixes for possible loss-of-protocol-sync issues, but it > doesn't seem like that would result in silent leakage; the symptoms > would be pretty obvious. > > Have you poked into the client-side state to see what that end thinks > it's doing with the idle connections? > > regards, tom lane >
Hi, I cannot confirm this. My "Idle in transaction" connections are all gone since updating to 1.8. The other reported problem concerning hanging update statements was solved by updating psycopgs2 with the patch mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=843723. My connection count is between 50 and 60 idle connections. In general it is working good now. I could also disable by nightly restart of spacewalk and it is running for several days now. Regards Patrick -- Lobster LOGsuite GmbH, Münchner Straße 15a, D-82319 Starnberg HRB 178831, Amtsgericht München Geschäftsführer: Dr. Martin Fischer, Rolf Henrich _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
