On 21/11/12 11:41, Shaun Thomas wrote:
On 11/20/2012 04:35 PM, Jeff Janes wrote:
Atomic update commit failure in the meatware :)
Ha.
What's actually funny is that one of the affected machines started
*swapping* earlier today. With 15GB free, and 12GB of inactive cache,
and vm.swappiness set to 0, it somehow decided there was enough memory
pressure to push 1.5GB of *something* into swap.
Frankly, the kernel we're using is clearly deranged. There's really no
other way to explain this. But we were blaming various elements of PG
for several weeks following our upgrade. After further examination,
our query profile isn't any different, and the load spikes were
effectively random.
All I can say is... be wary of the 3.2 kernel. It's... unique.
You'll just have to upgrade to Microsoft!
<Ducks, and runs away _VERY_ quickly!>
Could you not install a later kernel?
Cheers,
Gavin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
