Re: standby_schedule

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: standby_schedule
Date: 2016-03-30 00:11:04
Message-ID: CAB7nPqQ_x-dWecvVtiDXH_r9ssRykMkYUmXwPOfDTb7YiHkLXg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 30, 2016 at 6:44 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> I think we're at a point where we can translate the tests in
> src/test/regress/standby_schedule file into a PostgresNode-based test,
> or remove it (probably under src/test/recovery). That way, it would get
> run all the time rather than just when somebody feels like it (which is
> probably almost never, if at all).

Having a test in src/test/recovery feels the most natural approach to me.

> Would somebody like to volunteer?

After the CF is closed and feature freeze happens, I guess I could
always find a couple of hours for cleanup patches. FWIW, I have run
this test suite manually from time to time, but running it always in
the buildfarm would be way better (buildfarm client code is not
patched yet to run tests in src/test/recovery btw).
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-03-30 00:15:39 Re: Re: [COMMITTERS] pgsql: Sync tzload() and tzparse() APIs with IANA release tzcode2016c.
Previous Message Thomas Munro 2016-03-29 23:53:59 kqueue