On Wed, 26 Feb 2025 at 07:56, Michael Paquier <mich...@paquier.xyz> wrote:
> > This fix is not correct. No system function calls (well basically > most of them) or even more no PostgreSQL-specific calls should happen > while holding a spinlock. elog() is a good example of what not to do. > One example: imagine a palloc failure while holding this spinlock in > this elog(). Indeed. PFA the correct one. -- Best regards, Maxim Orlov.
v2-0001-Avoid-double-spinlock-release.patch
Description: Binary data
