Re: ERROR: cache lookup failed for user mapping 476444

2022-09-09 Thread shanker singh
 
  
Hi TEAM,
 
I am trying to delete an extension db2_fdw but getting  
 
ERROR:  cache lookup failed for user mapping 476444
 
  
 
Is there any solution or workaround for this error. 
 
  
 
Thanks and regards,
 
Shanker
 
  
 American Express made the following annotations 



"This message and any attachments are solely for the intended recipient and may 
contain confidential or privileged information. If you are not the intended 
recipient, any disclosure, copying, use, or distribution of the information 
included in this message and any attachments is prohibited. If you have 
received this communication in error, please notify us by reply e-mail and 
immediately and permanently delete this message and any attachments. Thank 
you." 


American Express a ajouté le commentaire suivant

Ce courrier et toute pièce jointe qu'il contient sont réservés au seul 
destinataire indiqué et peuvent contenir des renseignements confidentiels et 
privilégiés. Si vous n'êtes pas le destinataire prévu, toute divulgation, 
duplication, utilisation ou distribution du courrier ou de toute pièce jointe 
est interdite. Si vous avez reçu cette communication par erreur, veuillez nous 
en aviser par courrier et détruire immédiatement le courrier et les pièces 
jointes. Merci.

  

Re: ERROR: cache lookup failed for user mapping 476444

2022-09-09 Thread Tom Lane
shanker singh  writes:
> I am trying to delete an extension db2_fdw but getting  
> ERROR:  cache lookup failed for user mapping 476444

Hmm, seems like there must be a pg_depend entry claiming that that
user mapping depends on the extension; which it shouldn't, but ...

Is there a pg_depend row having objid = 476444?  What's in it?

regards, tom lane




Re: ERROR: cache lookup failed for user mapping 476444

2022-09-09 Thread Shanker Singh
Hi Tom, 
Thank you very much for the info. Pg-depend did had an entry for the above 
object. After deleting the entry the drop extension worked fine. Thank you very 
much for the help.

Regards,
Shanker

Sent from my iPhone

> On Sep 9, 2022, at 8:10 AM, Tom Lane  wrote:
> 
> shanker singh  writes:
>> I am trying to delete an extension db2_fdw but getting  
>> ERROR:  cache lookup failed for user mapping 476444
> 
> Hmm, seems like there must be a pg_depend entry claiming that that
> user mapping depends on the extension; which it shouldn't, but ...
> 
> Is there a pg_depend row having objid = 476444?  What's in it?
> 
>regards, tom lane





Re: Missing query plan for auto_explain.

2022-09-09 Thread Maxim Boguk
On Thu, Sep 8, 2022 at 1:18 PM Matheus Martin 
wrote:

> We do have JIT enabled `jit=on` with `jit_above_cost=10`.
>
> I am sorry but I don't quite understand what role JIT plays in
> this situation with `auto_explain`. Could you please elaborate on that?
>
>
In your log - time spent during the execution stage (where auto-exlain can
help) but during the bind/planning stage (e.g. generation of plan).
So you have a problem not with slow query execution, but with slow query
planning, so autoexplain cannot help in that case.
JIT is one possible explanation of planning stage slowdown.

Can you run explain (analyze, costs, buffers, timing) of your query?
And check how long the planning stage took and check if JIT was used or not
(and how much time spent during JIT if it had been used).



-- 
Maxim Boguk
Senior Postgresql DBA
https://dataegret.com/

Phone UA: +380 99 143 
Phone AU: +61  45 218 5678