Thoughts on linking to a static libduckdb?

[tristan957]

At Neon, we are going to deploy pg_duckdb for our users. As you all are no doubt familiar, there are other extensions using duckdb behind the scenes, including pg_mooncake. We have been offering pg_mooncake on the platform for a few months at this point, so it is the "incumbent". Both pg_mooncake and pg_duckdb install libduckdb.so into the same location in a Postgres installation, so it's a race to see whose libduckdb.so ends up in the Postgres installation tree. This problem manifests as unknown symbols because both projects pin different versions of pg_duckdb.

An easy solution is to just statically link DuckDB, which the build system already supports by producing a libduckdb_static.a. I'm not sure if you would want this to be the default or the only option. I don't really expect y'all as upstream to produce the PR yourselves since we are probably the first users to run into this, so I'm more just looking to see if y'all would accept a PR from Neon.