Y.

> I think this goal of this PR makes a lot of sense, but I think this needs a review from someone that's more experienced in C++ than me. @Y--...

> @Y-- Does this still make sense? Or should we close this one? It seems like you haven't needed this for your cleanup so far? Yeah I think something like...

Hi @theory, thanks for reporting the issue. Out of curiosity, why are you trying to bring the DuckDB library from https://github.com/duckdb/duckdb/releases/ ? `make install` in the `pg_duckdb` root directory should...

@wuputah do you still think we need this since we are using DuckDB's official `httpfs`? To me it feels like we would re-test an external library.

We were able to keep using Node 16 with: ``` env: ACTIONS_RUNNER_FORCE_ACTIONS_NODE_VERSION: node16 ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true ``` (from [this article](https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/) ) But that is likely to break very soon indeed. We...

This is a duplicate of https://github.com/duckdb/pg_duckdb/issues/761. We have a PR opened for it, will try to fix ASAP

Thanks @saygoodbyye. I haven't gotten a chance to come back to this one. I'll make sure to discuss this with @JelteF in the next few weeks.

Hi @saygoodbyye I'm looking into this one. I've tried to compile PG with the same options you've provided but got: ``` configure: WARNING: unrecognized options: --enable-crash-info ``` I've checked the...

The main error here seems to be `Failed to create directory "/var/lib/postgresql/.duckdb/extension_data"` - what happens if you create the folder? As @JelteF mentioned, the duckdb UI is not supported officially...

Right, you should be able to [`EXPOSE 4213`](https://docs.docker.com/reference/dockerfile/#expose) it in the docker file or when you run it you can use the `-p` flag to forward it ([ref](https://docs.docker.com/get-started/docker-concepts/running-containers/publishing-ports/)) Here's more...