pgsql: Fix overly large values/nulls arrays

From: David Rowley <drowley(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix overly large values/nulls arrays
Date: 2024-12-29 10:58:05
Message-ID: E1tRqzk-001wCe-L0@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix overly large values/nulls arrays

These arrays were sized with Natts_pg_trigger (19) when they should have
been sized with Natts_pg_event_trigger (7). We'd better fix this as
it's clearly a mistake and it could become problematic if
pg_event_trigger were to gain a dozen or so more columns in the future.

No backpatch as there's no actual bug and the column count on those
tables isn't going to change in released versions.

Author: Xin Zhang <zhanghien(at)qq(dot)com>
Discussion: https://postgr.es/m/tencent_05AD0FB321A414EC3661204D2102AA6EF605@qq.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/eb53ff5517e50018539747d75a02d493abc2d232

Modified Files
--------------
src/backend/commands/event_trigger.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2024-12-29 17:43:54 Re: pgsql: Replace BackendIds with 0-based ProcNumbers
Previous Message Tom Lane 2024-12-28 21:22:00 pgsql: Replace PGPROC.isBackgroundWorker with isRegularBackend.