libduckdb.so name is different for compilation and runtime

[AmebaBrain]

With a new 1.1.3 release it's required to rename libduckdb.so library to libduckdb.1.1.3.so to have compilation succeeded.

# Rename library file with version number
mv "libduckdb.${LIB_EXT}" "libduckdb.${DUCKDB_VERSION}.${LIB_EXT}"

But in the same time, during runtime the compiled duckdb_fdw.so still expects the duckdb library to be named as libduckdb.so and not libduckdb.1.1.3.so. Otherwise, it fails with

psql:/docker-entrypoint-initdb.d/fdw_setup.sql:1: ERROR:  could not load library "/usr/lib/postgresql/17/lib/duckdb_fdw.so": libduckdb.so: cannot open shared object file: No such file or directory

Is it expected behavior? Use libduckdb.1.1.3.so for the compilation but libduckdb.so during runtime?

[alitrack]

compiled in this way

export DUCKDB_VERSION=1.1.3
make USE_PGXS=1 
make USE_PGXS=1 install 

[AmebaBrain]

but for this to work you also have to have physically file libduckdb.1.3.3.so. otherwise you will get compilation error. and once compilation is done, you will have to have original libduckdb.so file back again. otherwise, compiled duckdb_fdw.so won't work