pgsql: Prepare for forthcoming LLVM 13 API change.

From: Thomas Munro <tmunro(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Prepare for forthcoming LLVM 13 API change.
Date: 2021-06-24 23:32:10
Message-ID: E1lwYpO-0005zm-Kg@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Prepare for forthcoming LLVM 13 API change.

LLVM 13 (due out in September) has changed the semantics of
LLVMOrcAbsoluteSymbols(), so we need to bump some reference counts to
avoid a double-free that causes crashes and bad query results.

A proactive change seems necessary to avoid having a window of time
where our respective latest releases would interact badly. It's
possible that the situation could change before then, though.

Thanks to Fabien Coelho for monitoring bleeding edge LLVM and Andres
Freund for tracking down the change.

Back-patch to 11, where the JIT code arrived.

Discussion: https://postgr.es/m/CA%2BhUKGLEy8mgtN7BNp0ooFAjUedDTJj5dME7NxLU-m91b85siA%40mail.gmail.com

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/6ada4fd06666cf778dacec0fb98d569760ffd70a

Modified Files
--------------
src/backend/jit/llvm/llvmjit.c | 3 +++
1 file changed, 3 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2021-06-24 23:43:13 pgsql: doc: Move remove_temp_files_after_crash to section for developer
Previous Message Thomas Munro 2021-06-24 23:32:00 pgsql: Prepare for forthcoming LLVM 13 API change.