On 09/13/2013 01:58 PM, Merlin Moncure wrote: > ok, points similar: > *) master/slave config (two slaves for me) > *) 'big' server 256GB mem, 32 core > *) 80% approx. (perhaps more) > *) some spacial searching (but not very much) > *) OLTP > *) presentation of load, although in my case it did resolve anywhere > from 30 secs to half hour > *) aside from the spike, 100% healthy > > points different > *) application side pooling: 96 app servers, max 5 connections each > (aside: are you using transaction mode pgbouncer?)
Yes. > *) I saw gripes about relation extension in pg_locks I'll check for that next time. We're also working on seeing if we can reproduce this under test conditions. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
