Re: pgbench tap tests & minor fixes

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Nikolay Shaplov <dhyan(at)nataraj(dot)su>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench tap tests & minor fixes
Date: 2017-05-08 19:07:16
Message-ID: alpine.DEB.2.20.1705082053430.3983@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Alvaro,

>> Here is a v3, with less files. I cannot say I find it better, but it
>> still works.
>>
>> The "command_likes" function has been renamed "command_checks".
>
> Do parts of this need to be backpatched?

I would not bother too much about backpatching.

> I notice that you're patching pgbench.c, probably to fix some bug(s);

The bug fix part is about small issues that I noticed while writing
extensive tests. Probably nobody would have noticed otherwise for some
time.

> is the idea that we would backpatch all the new tests on whatever old
> branches need the bugfixes too? If so, how far back do the fixes need to
> go?

I'd say 9.6. There has been quite some changes and significant
restructuring on pgbench wrt to prior versions.

> ISTM TestLib::command_checks() needs a comment explaining what it does.
> Its API seems pretty opaque.

Ok. That I can do. I'm wondering about Windows portability that I cannot
check.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-05-08 19:43:30 Re: Adding support for Default partition in partitioning
Previous Message Fabien COELHO 2017-05-08 18:51:36 Re: [Pkg-postgresql-public] Debian "postgresql-common" config check issue with pg10