From: Tom Lane <tgl@sss.pgh.pa.us>
To: rekgrpth@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex
Date: Thu, 07 Dec 2023 09:32:43 -0500
Message-ID: <1268114.1701959563@sss.pgh.pa.us> (raw)
In-Reply-To: <18233-98fe3f5ee55550ff@postgresql.org>
References: <18233-98fe3f5ee55550ff@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> coerce_type accepts NULL as pstate and can pass it to
> coerce_record_to_complex, which passes it to GetNSItemByRangeTablePosn,
> which dereferences it.
Can you demonstrate any actual bug here? If so, it's not
coerce_type's, which is clearly documented to allow NULL.
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, rekgrpth@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex
In-Reply-To: <1268114.1701959563@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