Re: Differential code coverage between 16 and HEAD - Mailing list pgsql-hackers

From David Rowley
Subject Re: Differential code coverage between 16 and HEAD
Date
Msg-id CAApHDvpBphq_K18RcCk8_rxvk6WE8tPw0w1yvBjg9V_tWiotTA@mail.gmail.com
Whole thread Raw
In response to [MASSMAIL]Differential code coverage between 16 and HEAD  (Andres Freund <andres@anarazel.de>)
Responses Re: Differential code coverage between 16 and HEAD
List pgsql-hackers
On Mon, 15 Apr 2024 at 10:33, Andres Freund <andres@anarazel.de> wrote:
> - The new bump allocator has a fair amount of uncovered functionality:
>   https://anarazel.de/postgres/cov/16-vs-HEAD-2024-04-14/src/backend/utils/mmgr/bump.c.gcov.html#L293

The attached adds a test to tuplesort to exercise BumpAllocLarge()

>   https://anarazel.de/postgres/cov/16-vs-HEAD-2024-04-14/src/backend/utils/mmgr/bump.c.gcov.html#L613

I don't see a way to exercise those. They're meant to be "can't
happen" ERRORs.  I could delete them and use BogusFree, BogusRealloc,
BogusGetChunkContext, BogusGetChunkSpace instead, but the ERROR
message would be misleading. I think it's best just to leave this.

David

Attachment

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Things I don't like about \du's "Attributes" column
Next
From: Michael Paquier
Date:
Subject: Re: Removing GlobalVisTestNonRemovableHorizon