| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: recovery is stuck when children are not processing SIGQUIT from previous crash |
| Date: | 2009-09-25 16:27:58 |
| Message-ID: | 20090925162758.GP3914@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Peter Eisentraut wrote:
> strace on the backend processes all showed them waiting at
>
> futex(0x7f1ee5e21c90, FUTEX_WAIT_PRIVATE, 2, NULL
>
> Notably, the first argument was the same for all of them.
>
> I gather that a futex is a Linux kernel thing, which is probably then
> used by glibc to implement some pthreads stuff. Anyone know more?
Maybe a backtrace from GDB would tell us more.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-26 16:19:47 | Re: recovery is stuck when children are not processing SIGQUIT from previous crash |
| Previous Message | Jakub Gołębiewski | 2009-09-25 16:04:56 | postgresql ldap integration 3DF8-644A-B923 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-09-25 17:25:35 | Re: Hot Standby 0.2.1 |
| Previous Message | Alvaro Herrera | 2009-09-25 16:13:37 | Re: syslog_line_prefix |