| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | pavel(dot)stehule(at)gmail(dot)com |
| Cc: | sawada(dot)mshk(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: plpgsq_plugin's stmt_end() is not called when an error is caught |
| Date: | 2022-12-15 08:34:41 |
| Message-ID: | 20221215.173441.1022417926121277385.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Thu, 15 Dec 2022 09:03:12 +0100, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote in
> I found some solution based by using fmgr hook
>
> https://github.com/okbob/plpgsql_check/commit/9a17e97354a48913de5219048ee3be6f8460bae9
Oh! Thanks for the pointer, will look into that.
By the way, It seems to me that the tool is using
RegisterResourceReleaseCallback to reset the function nest level. But
since there's a case where the mechanism doesn't work, I suspect that
the callback can be missed in some cases of error return, which seems
to be a bug if it is true..
# I haven't confirmed that behavior by myself, though.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sandro Santilli | 2022-12-15 08:52:34 | Re: Ability to reference other extensions by schema in extension scripts |
| Previous Message | Daniel Gustafsson | 2022-12-15 08:34:17 | Re: pg_upgrade: Make testing different transfer modes easier |