Op 6/17/26 om 16:39 schreef Nathan Bossart:
On Fri, Jun 12, 2026 at 04:54:04PM +0200, Álvaro Herrera wrote:
On 2026-Jun-04, Nathan Bossart wrote:
This code is ~18 years old, so I'm dubious there's a real problem here.
Does something like this suppress the warning?
Oid actual_arg_types[FUNC_MAX_ARGS] = {InvalidOid};
I agree that it doesn't look like there's a real problem, and that
something like what you suggest should silence this warning. I mildly
prefer to do " = {0}" though, the rules for C incomplete initializers
being so weird. But I wouldn't oppose this patch as posted.
WFM. Hans, can you confirm this fixes the issue?
FWIW, it silences that warning on my gcc 16.1.0
Erik
