Re: [HACKERS] [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd) - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: [HACKERS] [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd)
Date
Msg-id 01B7E461-9388-456A-AEDE-6237704018FD@yesql.se
Whole thread Raw
In response to Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" testpending solution of its timing is (fwd)  (David Steele <david@pgmasters.net>)
List pgsql-hackers
> On 8 Apr 2020, at 14:58, David Steele <david@pgmasters.net> wrote:
>
> On 3/28/20 5:27 AM, Fabien COELHO wrote:
>> Hello Tom,
>> Thanks for your feedback,
>>>> I'd be rather unclear about what the actual feedback is, though. I'd
>>>> interpret it as "pg does not care much about code coverage". Most clients
>>>> are in the red on coverage.postgresql.org. I'd like pgbench at least to be
>>>> in the green, but it does not look that it will ever be the case.
>>> The reason why the first iteration failed was that it was insufficiently
>>> insensitive to timing.
>
> This patch has been marked Returned with Feedback.
>
> If the TAP tests could be made to work without the special exceptions added to pgbench.c I think this patch would
havea better chance. 

Turns out it wasn't, but I'm doing that now since this has been stalled since.

cheers ./daniel


pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: proposal: possibility to read dumped table's name from file
Next
From: Amit Kapila
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions