Aldrin M.

thanks for the tip, I can try it out

so update share allows you to see a more recent snapshot of what's already available. create statements require write access and reconnection

from the docs, it doesn't seem like update share is enough to see catalog additions: https://motherduck.com/docs/motherduck-sql-reference/update-share/

Awesome, thank you!

I'm trying to figure out where that occurs (I suspect in the join order optimizer around query graph manager). I'm also wondering if I have an extension that translates to duckdb::LogicalOperator (which the optimizer accepts) then motherduck can still do hybrid execution downstream (since it sounds like it is an optimization rule)

i still appreciated the response :)