Re: emergency outage requiring database restart

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: emergency outage requiring database restart
Date: 2016-10-18 01:32:14
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 18/10/16 14:12, Michael Paquier wrote:
> On Tue, Oct 18, 2016 at 4:21 AM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-10-18 01:50:09 Re: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran
Previous Message Kyotaro HORIGUCHI 2016-10-18 01:30:51 Re: asynchronous execution