standby_schedule

Started by Alvaro Herreraabout 10 years ago4 messageshackers
Jump to latest
#1Alvaro Herrera
alvherre@2ndquadrant.com

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 Herrera http://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

#2Michael Paquier
michael@paquier.xyz
In reply to: Alvaro Herrera (#1)
Re: standby_schedule

On Wed, Mar 30, 2016 at 6:44 AM, Alvaro Herrera
<alvherre@2ndquadrant.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

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

#3Simon Riggs
simon@2ndQuadrant.com
In reply to: Alvaro Herrera (#1)
Re: standby_schedule

On 29 March 2016 at 22:44, Alvaro Herrera <alvherre@2ndquadrant.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).

Would somebody like to volunteer?

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

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/&gt;
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

#4Alvaro Herrera
alvherre@2ndquadrant.com
In reply to: Simon Riggs (#3)
Re: standby_schedule

Simon Riggs wrote:

On 29 March 2016 at 22:44, Alvaro Herrera <alvherre@2ndquadrant.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).

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 Herrera http://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