| From: | Daniel Hahler <postgresql(at)thequod(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #9721: Fatal error on startup: no free slots in PMChildFlags array |
| Date: | 2014-03-25 15:39:20 |
| Message-ID: | 5331A328.20103@thequod.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 25.03.2014 16:26, Alvaro Herrera wrote:
>> FWIW, I have just suspended and started the container manually, and
>> PostgreSQL kept running (upgraded to 9.3.4 in the meantime).
>>
>> Maybe it's a bug with OpenVZ and how it restores some resources after rebooting the host?
>
> Maybe it forgot to restore the shared memory state.
Shouldn't that have caused PostgreSQL to error out much earlier - and not after half an hour?
Anyway, maybe it won't affect 9.3.4 anymore, and it's good to know that it might just be related to rebooting with the "suspend" option.
Regards and thanks,
Daniel.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-03-25 16:02:53 | Re: BUG #9721: Fatal error on startup: no free slots in PMChildFlags array |
| Previous Message | Alvaro Herrera | 2014-03-25 15:26:06 | Re: BUG #9721: Fatal error on startup: no free slots in PMChildFlags array |