Re: Force testing of query jumbling code in TAP tests - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Force testing of query jumbling code in TAP tests
Date
Msg-id ZAGTh8akg0u/6Y1a@paquier.xyz
Whole thread Raw
In response to Re: Force testing of query jumbling code in TAP tests  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Feb 28, 2023 at 02:06:05PM +0900, Michael Paquier wrote:
> Are there any objections to do what's proposed in the patch and
> improve the testing coverage of query jumbling by default?

Well, done this one as of d28a449.  More validation tests could always
be added later if there are better ideas.  Coverage of this code has
gone up to 94.4% at the end:
https://coverage.postgresql.org/src/backend/nodes/queryjumblefuncs.funcs.c.gcov.html
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: Add SHELL_EXIT_CODE to psql
Next
From: vignesh C
Date:
Subject: Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher