Re: PL/pgSQL: FOUND is NULL, not false, in event trigger functions

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PL/pgSQL: FOUND is NULL, not false, in event trigger functions
Date: 2026-10-26 19:54:16
Message-ID: E8999E9D-7381-406C-82E0-69327EA17350@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 26 Oct 2026, at 20:45, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Given the lack of field complaints, I'm inclined to leave it as-is
> in released branches (maybe it's not too late for v19, though).

If we're leaving it as-is in backbranches, wouldn't it be better to opt for
consistency and leave it in 19 as well and only adjust the documentation?

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dongpo Liu 2026-10-26 20:13:30 Re: pg_*_advice: tsv load failure, etc.
Previous Message Tom Lane 2026-10-26 19:45:25 Re: PL/pgSQL: FOUND is NULL, not false, in event trigger functions