Re: BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: rekgrpth(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex
Date: 2023-12-07 14:32:43
Message-ID: 1268114.1701959563@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-12-07 18:50:01 BUG #18234: Nested Loop joint strategy is ignored for a tiny table joined with UNION ALL of two filtered parts
Previous Message Tom Lane 2023-12-07 14:30:45 Re: BUG #18232: Function pushJsonbValueScalar has not Assert(scalarVal) on WJB_KEY, WJB_VALUE and WJB_ELEM