Re: max_connections reached in postgres 9.3.3
От | Erik van Zijst |
---|---|
Тема | Re: max_connections reached in postgres 9.3.3 |
Дата | |
Msg-id | CA+69USssW-cZ7Q1x=ELVK-HxuXQeKB3xrFsjV7XGyKhYnV63yA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: max_connections reached in postgres 9.3.3 (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: max_connections reached in postgres 9.3.3
Re: max_connections reached in postgres 9.3.3 |
Список | pgsql-general |
On Thu, Jun 19, 2014 at 3:57 PM, Merlin Moncure <mmoncure@gmail.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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: