Re: emergency outage requiring database restart

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: emergency outage requiring database restart
Date: 2016-10-28 13:23:58
Message-ID: CAHyXU0wtTcWGn326YvUJ+abHGq7+s-d_M=EBsmuUv_NA2CYEEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 27, 2016 at 6:39 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
> On Thu, Oct 27, 2016 at 9:53 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>> I think we can rule out faulty storage
>
> Nobody ever expects the faulty storage

Believe me, I know. But the evidence points elsewhere in this case;
this is clearly application driven.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-10-28 13:25:03 Re: save redundant code for pseudotype I/O functions
Previous Message Robert Haas 2016-10-28 13:18:08 Re: Radix tree for character conversion