Jelte Fennema-Nio
Jelte Fennema-Nio
Why do use use `server_reset_query` in the first place? If it's because of prepared statements it's probably better to upgrade to PgBouncer 1.22.1 and set `max_prepared_statements=100`.
ah sorry, I didn't realize you didn't set `server_reset_query_always=1`. So in your case the `server_reset_query` is should be unused if you use transaction pooling.
Also, prepared transactions and prepared statements are two very different things (even though they both have similar names).
Also, it's worth trying 1.22.1 instead of 1.20.1, there have been some bugfixes since than that might fix this too.
> Not sure I would classify it as crude I mainly meant it was crude, because in theory there's no reason for Postgres to fully plan the query, we only...
I'll keep the issue open, since it would be great if this UDF was actually part of citus.
Like Marko said before, this indeed sounds useful, so a PR for this is definitely welcome. But it's not high on my own priority list. If you want this to...
What is your goal with running the duckdb UI from pg_duckdb? Why not use either plain duckdb, or use one of the many postgres UIs? In any case the duckdb...
If you're running it from within docker, you likely have to expose the port somehow to your host.