Jelte Fennema-Nio comments

Results 688 comments of


                                            Jelte Fennema-Nio

COPY duckdb_table FROM STDIN

I think the only way to make `COPY FROM STDIN` work is by implement more of the TAM interface. That we've not done that is more because it isn't needed...

With the TAM approach we'd indeed be constrained by Postgres its native COPY limitations. So indeed single threaded (unless users actively open more connections) and not supporting duckdb only formats...

Cannot access locally deployed minio using pg_duckdb

I guess this will be fixed by #151, once we implement it.

logical replication and auth_query issues

Ugh... That's indeed a bug... I think fixing it might not be too difficult though. I'll take a stab at doing so soonish. The only workaround that I can think...

Disappearing comments after undistributing table

Yeah, we'd definitely accept a fix (assuming it has some tests, and makes the change in the correct place in the codebase). Regarding pointers on this. I think you'd either...

Improve logging when per-user connection limit is hit

This does seem quite useful for debugging issues. @qris It's been a few years since you contributed this PR, do you still want to push this through?

Improve logging when per-user connection limit is hit

Closing this PR as it seems @qris seems to not be interested anymore, which is understandable. Thanks for the contribution.

Segmentation fault, use table partitioning。

Can you try with the latest commit from the `main` branch? We fixed a lot of crashes since 3.1.

DuckDBQueryOrThrow does not respond to cancel requests

Okay, so looking at the report, I think the main issue here is that our internal `DuckDBQueryOrThrow` function does not handle cancel requests (at all). That's indeed something we should...