Re: Contributing test cases to improve coverage

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: J F <jonathanfoo0523(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Contributing test cases to improve coverage
Date: 2024-06-13 14:01:23
Message-ID: daa90384-0085-4ac7-bbec-bcde1fc3ec1d@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12.06.24 18:44, J F wrote:
> (a) The regression test suite is run by a parallel scheduler, with some
> test cases dependent on previous test cases. If I just add my test case
> as part of the parallel scheduler’s tests, it might not work, since
> previous test cases in the scheduler might already create the same
> table, for instance.

Yes, you need to take care of that somehow. Some test files put all
their test objects in a schema. Others are careful to drop all test
objects at the end. Or you just have to pick non-conflicting names.

> (b) How do I get my test cases reviewed and ultimately included in a
> future release of PostgreSQL?

Perhaps start with

https://wiki.postgresql.org/wiki/Development_information

and in particular

https://wiki.postgresql.org/wiki/Submitting_a_Patch

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-06-13 14:40:20 Re: MultiXactMemberFreezeThreshold can make autovacuum *less* aggressive
Previous Message Ashutosh Bapat 2024-06-13 13:59:44 Re: Contributing test cases to improve coverage