On Thu, Jun 19, 2014 at 10:10 PM, Erik van Zijst <erik.van.zi...@gmail.com> wrote: > On Thu, Jun 19, 2014 at 3:57 PM, Merlin Moncure <mmonc...@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.
Also, that thread talks about slave databases (we're seeing these issues exclusively on our master). Is that RecoveryMightBeInProgress code applicable to masters, too? Cheers, Erik > 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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
