Re: Compiling C Extension Functions against PostgreSQL 12 - Mailing list pgsql-general

From Tom Lane
Subject Re: Compiling C Extension Functions against PostgreSQL 12
Date
Msg-id 15293.1588516010@sss.pgh.pa.us
Whole thread Raw
In response to Re: Compiling C Extension Functions against PostgreSQL 12  (TalGloz <glozmantal@gmail.com>)
Responses Re: Compiling C Extension Functions against PostgreSQL 12  (TalGloz <glozmantal@gmail.com>)
List pgsql-general
TalGloz <glozmantal@gmail.com> writes:
> Andrew Gierth wrote
>> I didn't see an easy way of disabling bitcode emission for a module,
>> though I think that has been discussed before.

After taking a quick look through pgxs.mk, it looks like you might
be able to do something like
    override with_llvm := no
in your Makefile before including the PG parts.

> Will the absence of LLVM bit-code files effect the functionality of my
> "seal_mean_cxx_v2.so" library in Postgresql12 or I just won't benefit from
> Postgres JIT compiler (postgresql12-llvmjit package)?

Should just prevent the possibility of "inline"-ing your functions
in JIT compilation.

> All the errors occurring for the llvm compilation part relate to the 
> Microsoft SEAL <https://github.com/microsoft/SEAL>   library that my
> seal_mean_cxx_v2.cpp uses. Since it is a third party library then maybe I
> should post the errors output there and see what they have to say about
> it...

Yeah, the ultimate solution is clearly over on that side.  These
last errors you've posted don't seem particularly Postgres-related.

            regards, tom lane



pgsql-general by date:

Previous
From: brajmohan saxena
Date:
Subject: Clustered Index in PG
Next
From: "Abraham, Danny"
Date:
Subject: Very frequent "Too many clients" eventually crashes postmaster