| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | depesz(at)depesz(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Backends "hanging" with strace showing selects? |
| Date: | 2010-11-15 19:52:16 |
| Message-ID: | 5421.1289850736@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Walden | 2010-11-15 19:55:21 | Re: Expected frequency of auto_vacuum activity |
| Previous Message | Tom Lane | 2010-11-15 19:36:17 | Re: index row requires 10040 bytes, maximum size is 8191 |