duckdb-postgres

Nice! Might this pave the way for an ADBC_scanner extension since I imagine the adbc and nanoarrow dependencies will be built in!? Similar to postgres_scanner, sqlite_scanner, odbc_scanner https://github.com/duckdblabs/postgres_scanner https://github.com/duckdblabs/sqlite_scanner https://github.com/rupurt/odbc-scanner-duckdb-extension

I've created an ODBC DuckDB extension to query any database that has an ODBC driver. It's modeled after the fantastic official Postgres scanner extension https://github.com/duckdblabs/postgres_scanner. It supports fetching rowsets in batches to minimize network overhead and defaults to the default DuckDB vector size of 2048. I've tested it against the IBM DB2 & Postgres ODBC drivers and will continue to test and add support for all major databases. If you've got one you'd like to see let me know in the comments. I've got plenty of improvements in the pipeline including: - Write to ODBC database - Predicate push down - Automatic catalog discovery - Performance benchmarks - Configurable batch size - Relative & absolute cursors - OS X builds using rosetta for databases without native aarch64 drivers (IBM/Oracle)

It's not a dumb question at all. I'm pretty knowledgeable with DBs and still find it very difficult to understand how many of these front-end/pass-through engines work. Checkout Postgres Foreign Data Wrappers. That might be the most well known approach for accessing one database through another. The Supabase team wrote an interesting piece about this recently. https://supabase.com/blog/postgres-foreign-data-wrappers-rus... You might also want to try out duckdb's approach to reading other DBs (or DB files). They talk about how they can "import" a sqlite DB in the above 0.7.0 announcement, but also have some other examples in their duckdblabs github project. Check out their "...-scanner" repos: https://github.com/duckdblabs/postgres_scanner https://github.com/duckdblabs/sqlite_scanner

Doesn't postgres have a columnar option? If so, you could prob get better performance for your analytical interactions if you switched some tables to columnar. Otherwise check out postgres scanner. https://github.com/duckdblabs/postgres_scanner They have a blog entry about it too: https://motherduck.com/blog/duckdb-ecosystem-newsletter-two/