| From: | Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PL/pgSQL: FOUND is NULL, not false, in event trigger functions |
| Date: | 2026-10-27 02:28:04 |
| Message-ID: | CAM2+6=U_sCd=A86GAr_iBF2k37U5CPYuK12PQz_M0J_qri3M=w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 27, 2026 at 2:46 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> > Ah, I misread and thought you were advocating for what you clearly
> wanted to
> > avoid. Given the lack of complaints then +1 for at most fixing in 19.
> > Backpatching takes a non-trivial amount of time, which really isn't a
> commodity
> > we have plenty of.
>
> Done that way, then.
>
Thanks, Tom.
>
> regards, tom lane
>
--
*Jeevan Chalke*
*Senior Principal Engineer, Engineering Manager*
*Product Development*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeevan Chalke | 2026-10-27 02:31:33 | Re: PL/pgSQL: fix validation of anycompatiblemultirange |
| Previous Message | Bruce Momjian | 2026-10-27 02:24:26 | Re: First draft of PG 19 release notes |