| From: | "Huang, Suya" <Suya(dot)Huang(at)au(dot)experian(dot)com> |
|---|---|
| To: | "Huang, Suya" <Suya(dot)Huang(at)au(dot)experian(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: DB sessions 100 times of DB connections |
| Date: | 2014-07-04 01:59:51 |
| Message-ID: | D83E55F5F4D99B4A9B4C4E259E6227CD014B3742@AUX1EXC01.apac.experian.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
BTW, I'm using the pgbadger report to check for peak connections/sessions.
From: pgsql-performance-owner(at)postgresql(dot)org [mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of Huang, Suya
Sent: Friday, July 04, 2014 11:44 AM
To: pgsql-performance(at)postgresql(dot)org
Subject: [PERFORM] DB sessions 100 times of DB connections
Hi,
We've experienced a DB issue yesterday and after checked the log found that the peak sessions is 3000 while the peak DB connections is only around 30. The application is having problem of pulling data but no warnings in DB log as it doesn't exceed max_connections.
How could this happen? How does sessions/connections work in Postgres?
Thanks,
Suya
| From | Date | Subject | |
|---|---|---|---|
| Next Message | piuschan | 2014-07-04 21:04:48 | stored procedure suddenly runs slowly in HOT STANDBY but fast in primary |
| Previous Message | Huang, Suya | 2014-07-04 01:44:02 | DB sessions 100 times of DB connections |