Open alex-ilyin opened 3 months ago
This looks like a problem within duckdb, they should return an error instead of letting the exception seep through the C api. Would you mind opening an issue there? I think posting the go code there should be good enough, but reproducing this in the REPL would be ideal for them I think.
I'm getting this exception from time to time when playing with DuckDB's memory limit and setting it so that my workload doesn't fit in. Looks like the problem is coming from the Go client and not from DuckDB itself. Here is the full error message (attaching stack trace below):
go-duckdb version used: 1.6.1
Here is the code I was executing. It doesn't return the error every time, usually it ends with an Out of Memory Error, which is expected
I used this dataset for my tests (Q4 2023): https://www.backblaze.com/cloud-storage/resources/hard-drive-test-data#downloadingTheRawTestData The only thing I did with it is merging all csvs into one using DuckDB CLI like that:
Here is the full stack trace I got: