Re: regression test for extended query protocol - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: regression test for extended query protocol
Date
Msg-id CAB7nPqRD5Dkm3RWjLEwiRPffN7eNcz3295wHC44ZSmKV_p8J3A@mail.gmail.com
Whole thread Raw
In response to Re: regression test for extended query protocol  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: regression test for extended query protocol  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Fri, Aug 5, 2016 at 12:21 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> If somebody had some spare time to devote to this, I would suggest to
> implement something in core that can be used to specify a list of
> commands to run, and a list of files-to-be-saved-in-bf-log emitted by
> each command.  We could have one such base file in the core repo that
> specifies some tests to run (such as "make -C src/test/recovery check"),
> and an additional file can be given by buildfarm animals to run custom
> tests, without having to write BF modules for each thing.  With that,
> pgsql committers could simply add a new test to be run by all buildfarm
> animals by adding it to the list in core.

Do you think about using a special makefile target to run those
commands, say in src/test? At the end we are going to need to patch
the buildfarm client code at least once, at least that would be worth
it in the long term..
-- 
Michael



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Detecting skipped data from logical slots (data silently skipped)
Next
From: Anastasia Lubennikova
Date:
Subject: Refactoring of heapam code.