On Thu, Sep 26, 2013 at 3:55 PM, Andres Freund <and...@2ndquadrant.com> wrote: > We have had several customers running postgres on bigger machines report > problems on busy systems. Most recently one where a fully cached > workload completely stalled in s_lock()s due to the *shared* lwlock > acquisition in BufferAlloc() around the buffer partition lock.
That's unfortunate. I saw someone complain about what sounds like exactly the same issue on Twitter yesterday: https://twitter.com/Roguelazer/status/382706273927446528 I tried to engage with him, but was unsuccessful. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
