Re: [sqlsmith] Failed assertion in joinrels.c - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: [sqlsmith] Failed assertion in joinrels.c
Date
Msg-id CAFiTN-scgPQWrtDCEppyt48Rkb84Xfqi7wuJFNjh4cQ1tRyogA@mail.gmail.com
Whole thread Raw
In response to Re: [sqlsmith] Failed assertion in joinrels.c  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers

On Tue, Aug 2, 2016 at 3:33 PM, Dilip Kumar <dilipbalaut@gmail.com> wrote:
There are many more such exposed functions, which can throw cache lookup failure error if we pass wrong value.

i.e. 
record_in
domain_in
fmgr_c_validator
edb_get_objecttypeheaddef
plpgsql_validator
pg_procedure_is_visible

Are we planning to change these also..

below query is one example (from sqlsmith).

ERROR:  cache lookup failed for procedure 0

postgres=# select

postgres-#                         pg_catalog.record_in(

postgres(#                           cast(pg_catalog.numerictypmodout(

postgres(#                             cast(98 as integer)) as cstring),

postgres(#                           cast(1 as oid),

postgres(#                           cast(35 as integer));

ERROR:  cache lookup failed for type 1

By mistake I mentioned edb_get_objecttypeheaddef function also, please ignore that.

So actual list is as below..

record_in
domain_in
fmgr_c_validator
plpgsql_validator
pg_procedure_is_visible

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: [sqlsmith] Failed assertion in joinrels.c
Next
From: Amit Kapila
Date:
Subject: Re: Broken order-of-operations in parallel query latch manipulation