Re: Bug 14592

From: Matthew Zinicola <mattzinicola(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(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 19:02:07
Message-ID: CA+PS-MdM3sJ7DpTbXw6jWH4biVCoNC0CEdqDKLGe1rRtvTsXzA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-www

Thanks, gentlemen. I've consulted the link about this and made one of the
two changes and I'm testing. I appreciate it, as I've never experienced
anything this (relative to postgres or systemd).. and I've been using
postgres for longer than I'd like to admit! :)

-Matt

On Wed, May 3, 2017 at 2:49 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:

> Magnus Hagander wrote:
>
> > 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).
>
> I checked the queue, and it expired long ago. These requests only live
> for a week.
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-05-03 20:50:20 Re: [pgsql-www] Bug 14592
Previous Message Alvaro Herrera 2017-05-03 18:49:49 Re: Bug 14592

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2017-05-03 20:50:20 Re: [pgsql-www] Bug 14592
Previous Message Alvaro Herrera 2017-05-03 18:49:49 Re: Bug 14592