Re: Backends "hanging" with strace showing selects?

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Backends "hanging" with strace showing selects?
Date: 2010-11-15 20:00:02
Message-ID: 20101115200001.GA18863@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 15, 2010 at 02:52:16PM -0500, Tom Lane wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> > hi
> > had strange situation today.
>
> > very high load, cpu saturated (and this machine has lots of cores).
>
> > i straced one of backends that was using lots of cpu (it was doing some
> > select, but I don't know what as i wasn't able to start psql).
>
> > strace looked like this:
> > select(0, NULL, NULL, NULL, {0, 1000}) = 0 (Timeout)
> > select(0, NULL, NULL, NULL, {0, 1000}) = 0 (Timeout)
> > select(0, NULL, NULL, NULL, {0, 1000}) = 0 (Timeout)
> > select(0, NULL, NULL, NULL, {0, 1000}) = 0 (Timeout)
>
> That suggests a lot of contention for a spinlock, but without any
> information about what the system was really doing, it's hard to go
> further than that.

we had ~ 700 active connections, but it is virtually impossible to tell
what they were doing, as I couldn't connect to get pg_stat_activity.

Best regards,

depesz

--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: depesz(at)depesz(dot)com / aim:depeszhdl / skype:depesz_hdl / gg:6749007

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dan Halbert 2010-11-15 20:01:03 Indexes on individual columns of composite primary key
Previous Message Matthew Walden 2010-11-15 19:57:59 Re: Expected frequency of auto_vacuum activity