Re: BUG #15746: cache lookup failed for function in plpgsql block - Mailing list pgsql-bugs

From r.zharkov@postgrespro.ru
Subject Re: BUG #15746: cache lookup failed for function in plpgsql block
Date
Msg-id 30da20dabeb7171ab31bf066caf69e7f@postgrespro.ru
Whole thread Raw
In response to Re: BUG #15746: cache lookup failed for function in plpgsql block  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-bugs
On 2019-04-11 19:11, Kyotaro HORIGUCHI wrote:
> Hello.
> 
> The cause is stale cast function id in cached expression of
> plpgsql. (get_cast_hashentry)
> 
> Happens since 9.5 to 11.  Once happens, the symptom persists
> until session-end. Doesn't happen on 9.4 since it doesn't cache
> cast expressions. 12 invalidates cached cast expressions
> (04fe805a17).
> 
> It seems to me possible that a cast calls a wrong function and
> leads to a crash. But I don't come up with a good way to fix
> this, but applying a part of the patch 04fe805a17 on 11(.2) seems
> working.
> 
> regards.

Hello,

Thank you! The patch works.

-- 
regards,
Roman Zharkov



pgsql-bugs by date:

Previous
From: r.zharkov@postgrespro.ru
Date:
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed
Next
From: Michael Paquier
Date:
Subject: Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker