| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Soni <diptatapa(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184 |
| Date: | 2019-04-23 03:31:25 |
| Message-ID: | 15430.1555990285@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Soni <diptatapa(at)gmail(dot)com> writes:
> Here's the backtrace. Please let me know if it helps.
> #4 OidFunctionCall1Coll (functionId=functionId(at)entry=1,
> collation=collation(at)entry=0, arg1=arg1(at)entry=75471) at fmgr.c:1325
hm, there's "function 1" ...
> #5 0x0000000000532054 in ProcedureCreate (procedureName=<optimized
> out>, procNamespace=procNamespace(at)entry=2200, replace=<optimized out>,
> returnsSet=returnsSet(at)entry=0 '\000',
> returnType=returnType(at)entry=2950, proowner=10,
> languageObjectId=languageObjectId(at)entry=13,
> languageValidator=languageValidator(at)entry=1,
... and that's where it's coming from. Seems like you have corrupt
data in pg_language. Might be entertaining to see what
"select * from pg_language" gives.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Soni | 2019-04-23 03:39:25 | Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184 |
| Previous Message | Soni | 2019-04-23 03:13:03 | Re: cache lookup failed for function 1 on fmgr_info_cxt_security, fmgr.c:184 |