| From: | "Vasudevan, Ramya" <ramya(dot)vasudevan(at)classmates(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Erik van Zijst <erik(dot)van(dot)zijst(at)gmail(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Borislav Ivanov <bivanov(at)atlassian(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Subject: | Re: max_connections reached in postgres 9.3.3 |
| Date: | 2014-07-14 17:41:15 |
| Message-ID: | 20EE50F73664E744AF948F0106FE6DFA2AD253DE@SEAMBX01.sea.corp.int.untd.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
We turned off NUMA in the BIOS on Jul 2nd and haven't seen the issue since - (though once last week, we had the connections count go up to 1000, but recovered in few seconds on its own). Will keep you all posted when I have more updates.
Appreciate everyone's help, comments and suggestions so far. Thank You.
Ramya
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2014-07-14 20:20:06 | Re: Why corruption memory in one database affects all the cluster? |
| Previous Message | Stephen Frost | 2014-07-14 12:05:41 | Re: security labels or sensitivity markings |