On 2026-Oct-03, Andres Freund wrote:
> - The intentional use of SIGQUIT shutdowns in a lot of tests leads to
> incomplete coverage
>
> That doesn't trigger gcov / lcov / genhtml errors, but it leads to things
> being assumed uncovered that aren't.
>
> Because we shut down a lot of tap test clusters with immediate mode, this
> actually has pretty large impact.
>
> I've experimented with replacing all the _exit() uses in the backend with
> something that triggers flushing of the coverage information in some cases
> that can be considered kinda maybe safe.
We had these threads about this problem
https://postgr.es/m/58ce1068-0cfc-3394-df69-ee0d03aaebb5%402ndquadrant.comhttps://postgr.es/m/816a4de5-3f15-4d66-1ec1-791cab2ca6df@gmail.com
but I don't think we did anything about that.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/