Erik van Zijst <erik.van.zijst@xxxxxxxxx> writes: > On Thu, Jun 19, 2014 at 3:57 PM, Merlin Moncure <mmoncure@xxxxxxxxx> 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. A descendant patch was applied: http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=1a3d104475ce01326fc00601ed66ac4d658e37e5 but that's only in 9.4, not any earlier branches. regards, tom lane
