Re: Recovery test failure for recovery_min_apply_delay on hamster

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Recovery test failure for recovery_min_apply_delay on hamster
Date: 2016-04-01 01:02:30
Message-ID: CAB7nPqQHoiUmH4dc_Psw5+29ftVyFGy1RLv=knsWsaYD2YWWzQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 1, 2016 at 4:14 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Noah Misch wrote:
>
>> The above-described topic is currently a PostgreSQL 9.6 open item. Alvaro,
>> since you committed the patch believed to have created it, you own this open
>> item.
>
> That's correct. Since we already had a patch available, I pushed it.
> I'll wait for a few days before marking the open item as closed in the
> wiki, to make sure that hamster reports success a few times.

Thanks. I just did a couple of additional manual tests on hamster, and
the sporadic failure does not show up anymore, so the daily runs
should be in good shape now for this test.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-04-01 01:06:23 Re: OOM in libpq and infinite loop with getCopyStart()
Previous Message Karl O. Pinc 2016-04-01 00:56:56 PQsendQuery+PQgetResult+PQsetSingleRowMode limitations and support