Re: BUG #9721: Fatal error on startup: no free slots in PMChildFlags array

Daniel Hahler <postgresql(at)thequod(dot)de> writes:
> On 25.03.2014 15:36, Alvaro Herrera wrote:
>> Tom Lane wrote:
>>> postgresql(at)thequod(dot)de writes:
>>>> PostgreSQL just failed to startup after a reboot (which was forced via
>>>> remote Ctrl-Alt-Delete on the PostgreSQL's containers host):

>>> ... in short, I want to see the rest of the log not just this part.

> That was the whole log.

Oh. So actually, "failed to startup" was a complete misdescription, and
what you should've said was "it appeared to be running normally, but I
saw this burst of weird messages in the postmaster log, so I decided to
restart it"?

I tend to concur with Alvaro's theory that OpenVZ must've failed to
restore the contents of shared memory precisely. If there were no other
symptoms than these, it seems like the misrestore must have affected just
a few small areas of the shared memory segment. Which seems odd, but then
again I know nothing of the internals of OpenVZ, so maybe it's a plausible
failure mode.

regards, tom lane