Re: [PATCH] Add tests for Bitmapset

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Greg Burd <greg(at)burd(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Add tests for Bitmapset
Date: 2025-10-01 05:00:59
Message-ID: CAApHDvrEPw6DAQdZg7u1YknVvN1Gy38kUURQm8bOHSKU2cw+4w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 1 Oct 2025 at 16:41, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Okay. Let's just remove as much code as possible, then. This is
> roughly what you have sent, minus the hardcoded empty set and the free
> calls. I'll just go do that in a bit.

Thanks. Just for reference, you may not need it if you're mostly done
already, but I had to finish this off in my head before moving on.
Feel free to ignore, but there are a couple of typos fixed at the very
least "varrying" should be "varying".

I didn't fully rationalise the tests in test_bitmapset.sql. There are
still a few which are duplicates due to '(b)' and NULL meaning the
same thing.

git diff --stat
.../test_bitmapset/expected/test_bitmapset.out | 400 ++------------
.../modules/test_bitmapset/sql/test_bitmapset.sql | 101 +---
.../modules/test_bitmapset/test_bitmapset--1.0.sql | 2 +-
src/test/modules/test_bitmapset/test_bitmapset.c | 605 +++++----------------
4 files changed, 222 insertions(+), 886 deletions(-)

I didn't look at the coverage report, but on thinking about it,
test_bitmapset.c's "PG_RETURN_NULL(); /* invalid input */" won't be
covered as I stripped out all the tests which purposefully pass
invalid input. You may not want it that way if you're keen to keep the
coverage of the test module high as well as bitmapset.c

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-10-01 05:01:09 Re: Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
Previous Message Hayato Kuroda (Fujitsu) 2025-10-01 04:38:42 RE: Resetting recovery target parameters in pg_createsubscriber