Re: test_json_parser/002_inline is kind of slow

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: test_json_parser/002_inline is kind of slow
Date: 2025-09-26 15:49:51
Message-ID: CAOYmi+mkQp6-cxwe+9gB=7ARo2EHROyfj3kChJ9n3G+gSLptvg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 26, 2025 at 8:38 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> You can just support running multiple tests with one run of the executable,
> e.g. by splitting the input / output on null bytes.

Yeah, but that doubles down on the bad unit test architecture... and I
don't think anyone would want to touch that code after I wrote it. But
it could be a quicker fix, especially if people are nervous about
moving to C+TAP.

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-09-26 15:51:26 Re: test_json_parser/002_inline is kind of slow
Previous Message David Christensen 2025-09-26 15:49:25 Re: [PATCH] GROUP BY ALL