From: Tom Lane <tgl@sss.pgh.pa.us>
To: pm91.arapov@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18848: DEREF_AFTER_NULL.EX.COND After having been compared to a NULL
Date: Fri, 14 Mar 2025 10:27:07 -0400
Message-ID: <3055350.1741962427@sss.pgh.pa.us> (raw)
In-Reply-To: <18848-62f448851e967b5c@postgresql.org>
References: <18848-62f448851e967b5c@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Looks like there is inconsistency with 'ind_name' and 'int_type' checks. In
> one place both are checked. In other place only the second one is checked.
> It's possible that when the second is not NULL the first is also not NULL.
> If this is so then the problem is not real. But it's hard to prove this. In
> any case the code needs to be made more clear.
Perhaps it needs to be made more clear, but this patch seems like no
improvement. Adding that Assert accomplishes nothing --- the code
will dump core if ind_name is null, with or without an Assert.
Given the lack of field complaints, I'm inclined to believe there's
not a bug here.
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, pm91.arapov@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18848: DEREF_AFTER_NULL.EX.COND After having been compared to a NULL
In-Reply-To: <3055350.1741962427@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