Re: BUG #19627: 32,768 trigger arguments wrap `tgnargs` and are silently lost at runtime

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: v3rdant(dot)xiang(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19627: 32,768 trigger arguments wrap `tgnargs` and are silently lost at runtime
Date: 2026-08-20 00:40:58
Message-ID: aoZNGjF08yM7A8w9@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Aug 19, 2026 at 02:22:10PM +0900, Michael Paquier wrote:
> As a side exercise, I have been looking at other catalogs with
> smallints like this one. There are quite a few (proc, index,
> partition keys, but triggers look like the only hole of this kind we
> had.
>
> Will fix that. Thanks for the report and the patch.

One s/INT16_MAX/PG_INT16_MAX/ later, done.

Note: The patch had two whitespace issues, with git diff --check
complaining.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Zexin Li 2026-08-20 01:28:53 Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
Previous Message Michael Paquier 2026-08-19 23:37:05 Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column