| From: | r(dot)zharkov(at)postgrespro(dot)ru |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15746: cache lookup failed for function in plpgsql block |
| Date: | 2019-04-12 03:22:09 |
| Message-ID: | 30da20dabeb7171ab31bf066caf69e7f@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-04-12 03:32:50 | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |
| Previous Message | r.zharkov | 2019-04-12 02:44:04 | Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed |