| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andreas Seltenreich <seltenreich(at)gmx(dot)de>, Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [sqlsmith] Failed assertion in joinrels.c |
| Date: | 2016-08-02 10:03:45 |
| Message-ID: | CAFiTN-v5R5OLV=daTRaQVgNeAshY686-gS+vC--04EDn9dGqDQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jul 30, 2016 at 4:27 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2016-08-02 10:20:07 | Re: [sqlsmith] Failed assertion in joinrels.c |
| Previous Message | Amit Kapila | 2016-08-02 09:51:41 | Re: Why we lost Uber as a user |