Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex
Date
Msg-id 1268114.1701959563@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Tree view 
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

pgsql-bugs by date:

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