Jelte Fennema-Nio
Jelte Fennema-Nio
Sounds like an issue with DigitialOcean, changing `max_prepared_statements` to a non-zero value by default. You should contact their support. Or possibly you can remove pgbouncer=true from the connection string and...
> I already removed pgbouncer=true but the errors persist (randomly) Did you remove it from all clients/applications talking to PgBouncer, because if one still has `pgbouncer=true` then that poisons connections...
> @JelteF In your experience, what is the correct way to recover PgBouncer when one gets a `prepared statement \"PGBOUNCER_34\" does not exist` error message, meaning that PgBouncer thinks there...
Another way to work around this is by wrapping the iceberg scans in subqueries. So the query in the original issue would look like this: ```sql select * from (from...
FYI this will likely be fixed by DuckDB 1.2.0 due to https://github.com/duckdb/duckdb/pull/15843 being merged
Seems like a reasonable addition. Feel free to create a PR.
For which derives are you interested in this specifically?
Ah, okay yeah that does seem annoying. I think for operators it indeed makes sense to add track_caller. Could you send a PR for that?
To clarify I don't think this needs to be an optional feature, but can simply be done always for `add` and `mul` derives.
I think @sornas oversimplified the example a bit too much, because indeed you wouldn't be able to ever construct such a struct afaict. But something like this is completely valid...