[pgpool-hackers: 1432] Need guidance to track down an issue in 3.5.0

Devrim GÜNDÜZ devrim at gunduz.org
Mon Feb 29 04:30:07 JST 2016


I got an email offlist about 3.5.0 update (it was about the RPMS first), --
They said updating from 3.4.3 to 3.5.0 caused 100% CPU usage, also the queries

They downgraded to 3.4.3, and their problems disappeared.

They are willing to deploy 3.5.0 to production, to track down the issue. How
should they debug it? Any guidance?

Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20160228/f7448067/attachment.sig>

More information about the pgpool-hackers mailing list