Re: Missing program_XXX calling in pgbench tests - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Missing program_XXX calling in pgbench tests
Date
Msg-id f145c684-1ed4-4281-976e-20d2bdf7c956@eisentraut.org
Whole thread Raw
In response to RE: Missing program_XXX calling in pgbench tests  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List pgsql-hackers
On 12.06.25 05:23, Hayato Kuroda (Fujitsu) wrote:
>> +1 to focusing on the 0001 patch.
>>
>> Since this isn't a bug fix, I'm not sure back-patching is strictly necessary.
>> That said, it does improve consistency and test coverage, e.g., by adding checks
>> like help text length, so I'd be fine with back-patching if others see value in it.
> 
> Initially I thought this was helpful even for back branches, but it is not
> 100% needed.
> No objections even if it is only applied to master - it can check new features in
> future.

committed




pgsql-hackers by date:

Previous
From: Yugo Nagata
Date:
Subject: Re: Prevent internal error at concurrent CREATE OR REPLACE FUNCTION
Next
From: Fujii Masao
Date:
Subject: Re: tab complete for COPY populated materialized view TO