Re: [PATCH] Improve code coverage of network address functions

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Improve code coverage of network address functions
Date: 2025-01-20 21:39:40
Message-ID: CAOYmi+kx8eOmKj01dV4vSBeq9pvqR8dt6rGw+B_pBOE2_GOj+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 20, 2025 at 12:27 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Part of my thought here is that these functions are not worth their
> very own TAP test, with all the overhead that implies of firing up
> a new database instance. So I was looking for something we could
> fold them into.

By themselves, yeah, probably not. Having a separate place for a
TCP-focused suite might decrease the activation energy for testing
other network features, though.

In any case, Aleksander, I don't mean to sign you up for all that; the
`ssl` suite also seems good enough to me if you're interested in
pursuing that side of the patch further.

Thanks!
--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2025-01-20 21:45:00 Re: Statistics Import and Export
Previous Message Jeff Davis 2025-01-20 21:39:35 Re: Update Unicode data to Unicode 16.0.0