Postgres Pro
Downloads
Home   >   mailing lists

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-v5R5OLV=daTRaQVgNeAshY686-gS+vC--04EDn9dGqDQ@mail.gmail.com
Whole thread Raw
In response to Re: [sqlsmith] Failed assertion in joinrels.c  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [sqlsmith] Failed assertion in joinrels.c  (Dilip Kumar <dilipbalaut@gmail.com>)
Re: [sqlsmith] Failed assertion in joinrels.c  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view

On Sat, Jul 30, 2016 at 4:27 AM, Michael Paquier <michael.paquier@gmail.com> wrote:
OK for me. Thanks for the commit.

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



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

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Why we lost Uber as a user
Next
From: Dilip Kumar
Date:
Subject: Re: [sqlsmith] Failed assertion in joinrels.c