Josh Wills
Josh Wills
Ah okay, so it looks like the initial doubling (from an empty DB file to a re-run of an existing file) is a known issue and is related to 1)...
The fact that it keeps increasing on windows surprises me tho, going to see if there is something i can find about it in the discord...
It doesn't grow because DuckDB re-uses the unallocated disk space that it originally allocated in order to perform [MVCC](https://en.wikipedia.org/wiki/Multiversion_concurrency_control) operations when it loaded the seed file.
Looks like a mechanism to shrink the DB size via checkpoints is on the way: https://github.com/duckdb/duckdb/pull/7824
Hey Nuno! I don't know if that is feasible; as I understand it, `dbt` only supports incremental materialization against the `table` materialization type. The only way to do it, I...
huh, k-- these kinds of issues are very hard for me to debug since I don't have ready access to the environment in question; I think the best bet here...
Hrm-- maybe related to this? https://github.com/duckdb/duckdb/issues/6563
Ah, good to know-- and nice detective work!
Thinking I should add some logging in that `_load_aws_credentials` function to note which keys were set via the sts token call (tho obviously not the values) to help future folks...
...and also that it's possible that this extension may run into some of the same issues: https://github.com/duckdblabs/duckdb_aws