On Tue, Aug 2, 2016 at 6:03 AM, Dilip Kumar <dilipbal...@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 > plpgsql_validator > pg_procedure_is_visible > > Are we planning to change these also..
I think if they are SQL-callable functions that users can invoke from a SQL prompt, they shouldn't throw "cache lookup failed" errors or, for that matter, any other error that is reported with elog(). Now, I don't necessarily think that these functions should return NULL in that case the way we did with the others; that's not a sensible behavior for a type-input function AFAIK. But we should emit a better error. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
