Re: seawasp failing, maybe in glibc allocator

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seawasp failing, maybe in glibc allocator
Date: 2021-06-19 09:37:43
Message-ID: CA+hUKGLVZrZTQjWJdjTLe0Do4scskb7JgtBY-7UVQfOPmr+seA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 19, 2021 at 5:07 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> if (error != LLVMErrorSuccess)
> LLVMOrcDisposeMaterializationUnit(mu);
>
> +#if LLVM_VERSION_MAJOR > 12
> + for (int i = 0; i < LookupSetSize; i++)
> + LLVMOrcRetainSymbolStringPoolEntry(symbols[i].Name);
> +#endif

(Though, erm, that code probably either needs to move a bit further up
or become conditional, considering the error case immediately above
it, not sure which...)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-06-19 09:51:05 Re: locking [user] catalog tables vs 2pc vs logical rep
Previous Message Amit Kapila 2021-06-19 09:18:14 Re: Fix for segfault in logical replication on master