Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184 - Mailing list pgsql-general

From Tom Lane
Subject Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184
Date
Msg-id 3982.1555941867@sss.pgh.pa.us
Whole thread Raw
In response to cache lookup failed for function 1 on fmgr_info_cxt_security,fmgr.c:184  (Soni <diptatapa@gmail.com>)
Responses Re: cache lookup failed for function 1 on fmgr_info_cxt_security,fmgr.c:184  (Soni <diptatapa@gmail.com>)
List pgsql-general
Soni <diptatapa@gmail.com> writes:
> When "create extension "uuid-ossp"", I got :
> 2019-04-22 02:41:53.323 UTC [10305] XX000ERROR:  XX000: cache lookup
> failed for function 1
> 2019-04-22 02:41:53.323 UTC [10305] XX000LOCATION:
> fmgr_info_cxt_security, fmgr.c:184
> 2019-04-22 02:41:53.323 UTC [10305] XX000STATEMENT:  create extension
> "uuid-ossp" ;

That is just bizarre.  uuid-ossp's installation script does nothing
beyond a few simple CREATE FUNCTION commands, so it's really hard to
see how you could be getting to an incorrect function call.

Do you perhaps have any other extensions installed that could be
running add-on code during DDL commands?  I'm thinking of pgaudit
or auto_explain or the like.  If so, try disabling those to see
if the problem goes away.

If that's not it, could we trouble you to get a stack trace of
this problem?  Set a breakpoint at errfinish, run the CREATE
EXTENSION, and when it stops send us the output of "bt".
(Make sure that fmgr_info_cxt_security appears one or two levels
down in the trace, else you stopped at the wrong message output.)

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

            regards, tom lane



pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: orafce error
Next
From: Adrian Klaver
Date:
Subject: Re: cache lookup failed for function 1 on fmgr_info_cxt_security,fmgr.c:184