SQL Error [XX000]: FATAL: failed to open bitcode file "/usr/local/lib/postgresql/bitcode/vector/src/vector.bc": No such file or directory about pgvector HOT 4 CLOSED

@FrankyCTY Do you have jit set to on? (SHOW jit;)? Try disabling it and see if it fixes the query (SET jit to off; in the same session).

from pgvector.

May I know how jit causing problem? Because I will be looking into if it will be the same problem for our managed database (Google cloud sql) as it seems also have jit set to on.

Likely a packaging issue on your side. You might have these sorts of errors if the bitcode file is unreadable for any reason or corrupted, or if the extension was built with a newer clang version than the server, leading to newer bitcode files to be attempted to be read the older libllvm.so that the server is linked against.

from pgvector.

@FrankyCTY Do you have jit set to on? (SHOW jit;)? Try disabling it and see if it fixes the query (SET jit to off; in the same session).

Thanks for the reply.

I am a bit new to postgres, and I have ran SET jit to off; and ensure SHOW jit; return off afterwards in my postgres docker instance's database, and it didn't work.

Then I tried to update the parameter in postgresql.conf to set the jit to off, and related the conf by running SELECT pg_reload_conf();. Afterwards the problem is resolved. Maybe I should have reloaded the conf in the above attempt.

May I know how jit causing problem? Because I will be looking into if it will be the same problem for our managed database (Google cloud sql) as it seems also have jit set to on. (Update: Seems like Cloud sql does not support IIVM anyway so the paramter should be ignored. https://cloud.google.com/sql/docs/postgres/features#:~:text=Low%2DLevel%20Virtual%20Machine%20(LLVM)%20Just%2Din%2DTime%20(JIT)%20compilation.)

Thanks a lot, I appreciate that.

Directly set jit to off within the database session

local-console=# SHOW jit;
 jit
-----
 on
(1 row)

### Setting `jit` to off within the database instance
local-console=# set jit to off;
SET
local-console=# SHOW jit;
 jit
-----
 off
(1 row)

Updating the postgresql.conf to set jit to off then reload the config

sed -i 's/^#jit = on.*$/jit = off/' ./postgresql.conf

You are now connected to database "local-console" as user "postgres".
local-console=# SELECT pg_reload_conf();
 pg_reload_conf
----------------
 t
(1 row)

local-console=# show jit;
 jit
-----
 off
(1 row)

from pgvector.

Thanks guys, closing the issue now 💯

from pgvector.