Re: Bug 14592

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Matthew Zinicola <mattzinicola(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, PostgreSQL www <pgsql-www(at)postgresql(dot)org>
Subject: Re: Bug 14592
Date: 2017-05-03 18:44:06
Message-ID: CABUevEzQeOvL-=O4or10YLEbT4rH=uS-R6YwCGXk2YzHZxYx3Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-www

On Wed, May 3, 2017 at 8:20 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Wed, May 3, 2017 at 10:59 AM, Matthew Zinicola <mattzinicola(at)gmail(dot)com>
> wrote:
>
>> Any update on this issue? It is a server crash that I continue to
>> experience daily with 9.6.2.
>>
>> If a fix isn't forthcoming, can I safely downgrade to 9.5.6?
>>
>
> ​I see initial reports for bugs 14591 and 14593 - but nothing for
> 14592...which should have been issued roughly March 16th.
>
> https://www.postgresql.org/list/pgsql-bugs/2017-03/
>
> I'm adding -www since a form submission the results in a bug number should
> appear in our archives.
>
>
Bug reports go through the general mailinglist moderation steps. My guess
is that either the bug report was accidentally rejected by moderators, or
it was missed for long enough that it expired (unless it's still sitting in
the queue, but that seems unlikely given the approximate dates).

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2017-05-03 18:49:49 Re: Bug 14592
Previous Message Alvaro Herrera 2017-05-03 18:42:44 Re: Bug 14592

Browse pgsql-www by date

  From Date Subject
Next Message Alvaro Herrera 2017-05-03 18:49:49 Re: Bug 14592
Previous Message Alvaro Herrera 2017-05-03 18:42:44 Re: Bug 14592