| From: | "Vasudevan, Ramya" <ramya(dot)vasudevan(at)classmates(dot)com> |
|---|---|
| To: | Borislav Ivanov <bivanov(at)atlassian(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: max_connections reached in postgres 9.3.3 |
| Date: | 2014-06-19 23:14:05 |
| Message-ID: | 20EE50F73664E744AF948F0106FE6DFA2AD117EA@SEAMBX01.sea.corp.int.untd.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Borislav – Thank You for the update and all the information. It does look like we are on the same boat. And I feel the same too - maxing out on max_connections is just a symptom. pgbouncer may help alleviate the problem (though in your case it didn’t) and is definitely good to have either way.
One thing I wanted to mention is that we upgraded from CentOS 5.6 to 6.3 in order to fix a kernel bug we hit on 5.6. It was only after we moved to 6.3 that we started seeing issues with max_connections. And it is worth mentioning that there was no application change when we moved from 5.6 to 6.3. We then upgraded to 6.5 and still have the same problem. And from your case, 6.4 also has the same problem. I think that is why we wanted to downgrade to 5.8 to see if it resolves the issue.
Thank You
Ramya
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Borislav Ivanov | 2014-06-20 00:26:37 | Re: max_connections reached in postgres 9.3.3 |
| Previous Message | Merlin Moncure | 2014-06-19 22:57:22 | Re: max_connections reached in postgres 9.3.3 |