Robert Richter

This one (under [Initializing](https://duckdb.org/docs/api/nodejs/overview#initializing)): 

Same here ... but not just with S3

I fear it is not fixed. 

@carlopi Sure, I reduced my code to a minimal example here: [Memory Leak Demonstration](https://github.com/rrcomtech/duckdb-node-memory-leak) It creates 128 workers that create random data and send it to the main thread that...

No, sadly not. What I did was to instead write to a PostgreSQL and then sync both DBs periodically.

Currently, the setup experiences some compilation issues. Commands ran: ```bash nix-shell mkdir cmake-build-debug && cd cmake-build-debug cmake ``` CMake Log ``` -- The C compiler identification is Clang 14.0.6 --...

Concerning the CI, there should be no problem right now. Nix can be used by those who are willing to do so, but it is just an abstraction layer on...

> Most brew users tend to always the latest LLVM installed. But testing an alpine nix run and a further nix run on both MacOS systems should cover pretty much...

I just spotted the following when running ```bash nix-shell env ``` You'll find the following entry `NIX_HARDENING_ENABLE`: ``` NIX_HARDENING_ENABLE=fortify fortify3 stackprotector pic strictoverflow format relro bindnow ```

Current GCC setup worked in NixOS docker image ✅ ```bash docker run -it --rm nixos/nix git clone --recursive https://github.com/rrcomtech/hyrise-histograms.git --branch nixsetup hyrise && cd hyrise nix-shell cmake -GNinja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_COMPILER=gcc...