Daniel Hahler wrote:
> On 25.03.2014 15:36, Alvaro Herrera wrote:
> > Here's my guess --- this is a virtualized system that somehow dumped
> > some state to disk to hibernate while the host was being rebooted; and
> > then, when the host was up again, it tried to resurrect the virtual
> > machine and found things to be all inconsistent.
>
> Yes, the container was frozen during reboot:
>
> From the host:
> Mar 25 11:54:48 HN kernel: [ 76.237452] CT: 144: started
> Mar 25 11:55:03 HN kernel: [ 91.201145] CT: 144: restored
>
> OpenVZ uses "suspend" by default to stop containers on host reboots.
> I will change this to "stop" for the PostgreSQL container, but still this seems like something PostgreSQL should
handlebetter.
Of course. We will accept your patch as soon as you discover the bug.
Thanks for the offer.
> 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.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
