| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Marko Kreen <markokr(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [ADMIN] recovery is stuck when children are not processing SIGQUIT from previous crash |
| Date: | 2009-12-16 15:55:49 |
| Message-ID: | 20091216155549.GC4156@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Peter Eisentraut escribió:
> Here is a set of patches to address this issue.
>
> The first one is a small refactoring of the signal setting portability
> business.
This one looks like should be applied immediately to get some buildfarm
coverage (and alpha3)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-16 16:35:53 | Re: [ADMIN] recovery is stuck when children are not processing SIGQUIT from previous crash |
| Previous Message | Peter Eisentraut | 2009-12-16 15:48:44 | Re: [ADMIN] recovery is stuck when children are not processing SIGQUIT from previous crash |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-12-16 16:09:13 | Re: PostgreSQL project policy compendium |
| Previous Message | Robert Haas | 2009-12-16 15:53:30 | Re: PostgreSQL project policy compendium |