From: Tom Lane <tgl@sss.pgh.pa.us>
To: dan-eli@mail.ru
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18787: pointer te->defn not checked for NULL
Date: Tue, 28 Jan 2025 10:00:05 -0500
Message-ID: <1124699.1738076405@sss.pgh.pa.us> (raw)
In-Reply-To: <18787-676496fef9742cab@postgresql.org>
References: <18787-676496fef9742cab@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Here is a patch fixing the issue. I think that NULL check is needed here
In none of these three bug reports have you given an actual
bug report --- that is, there is no reason to believe that
these patches fix any reachable failure case. If you have
examples showing that the cases are reachable, please
provide those first, and then we can discuss suitable fixes.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, dan-eli@mail.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18787: pointer te->defn not checked for NULL
In-Reply-To: <1124699.1738076405@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox