David Kerr <dmk@xxxxxxxxxxxxxx> writes: > Looks like it was a query that was running. once my developer killed it the CPU went back down. > I'm a little surprised by that, the backend process for that developer wasn't taking up a lot of CPU, > just the postmaster itself. The backtrace you showed was most definitely from a backend, not the postmaster. I think you misidentified the process. On some platforms "ps" isn't tremendously helpful about telling them apart ... regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
