Re: [HACKERS] standby_schedule

2016-03-30 Thread Alvaro Herrera 
Simon Riggs wrote:
> On 29 March 2016 at 22:44, Alvaro Herrera  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).
> >
> > Would somebody like to volunteer?
> 
> That was under my maintenance, so I'm happy to do that, as long as its
> after freeze.

That works for me -- this is not a "feature" as such.

-- 
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] standby_schedule

2016-03-30 Thread Simon Riggs 
On 29 March 2016 at 22:44, Alvaro Herrera  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).
>
> Would somebody like to volunteer?
>

That was under my maintenance, so I'm happy to do that, as long as its
after freeze.

-- 
Simon Riggshttp://www.2ndQuadrant.com/

PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: [HACKERS] standby_schedule

2016-03-29 Thread Michael Paquier 
On Wed, Mar 30, 2016 at 6:44 AM, Alvaro Herrera
 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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] standby_schedule

2016-03-29 Thread Alvaro Herrera 
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).

Would somebody like to volunteer?



-- 
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers