| From: | Erik van Zijst <erik(dot)van(dot)zijst(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Cc: | Borislav Ivanov <bivanov(at)atlassian(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, "Vasudevan, Ramya" <ramya(dot)vasudevan(at)classmates(dot)com> |
| Subject: | Re: max_connections reached in postgres 9.3.3 |
| Date: | 2014-06-20 05:10:19 |
| Message-ID: | CA+69USssW-cZ7Q1x=ELVK-HxuXQeKB3xrFsjV7XGyKhYnV63yA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jun 19, 2014 at 3:57 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> In your case user% is dominating system load. Along with the high cs
> this is really suggesting spinlock contention. A 'perf top' is
> essential for identifying the culprit. It's very possible that 9.4
> will fix your problem...see:
> http://postgresql.1045698.n5.nabble.com/Cpu-usage-100-on-slave-s-lock-problem-td5768655.html.
> There was some poorly optimized code in the wal replay.
Did that patch go in? The mailing list thread doesn't seem conclusive.
Cheers,
Erik
> merlin
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik van Zijst | 2014-06-20 05:58:42 | Re: max_connections reached in postgres 9.3.3 |
| Previous Message | Borislav Ivanov | 2014-06-20 00:26:37 | Re: max_connections reached in postgres 9.3.3 |