Re: emergency outage requiring database restart - Mailing list pgsql-hackers

From Gavin Flower
Subject Re: emergency outage requiring database restart
Date
Msg-id 1c54cf65-e9c0-40ea-4cbb-2bc602842910@archidevsys.co.nz
Whole thread Raw
In response to Re: emergency outage requiring database restart  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 18/10/16 14:12, Michael Paquier wrote:
> On Tue, Oct 18, 2016 at 4:21 AM, Alvaro Herrera
> <alvherre@2ndquadrant.com> wrote:
>> Merlin Moncure wrote:
>>
>>> We had several good backups since the previous outage so it's not
>>> clear the events are related but after months of smooth operation I
>>> find that coincidence highly suspicious. As always, we need to suspect
>>> hardware problems but I'm highly abstracted from them -- using esx +
>>> san.
>> Ah, so you're subject not only to hardware flaws but also to
>> virtualization layer bugs :-)
> Wait a couple of more years, and we'll get more complains about
> Postgres running in containers running in VMs. Even more fun waiting
> ahead.

that started life on different hardware with a different O/S





pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: asynchronous execution
Next
From: Michael Paquier
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran