Let Postgres own the Iceberg catalog and delegate analytics to DuckDB.
@denismagda5.1K followers
28,597 views
10 Comments
Comments from the original post on X (Twitter)

@Data_ls_Life
Just use DuckLake
2 likes

@denismagda
Does it let me query and join transactional data stored in Postgres with historical data in the lakehouse?
1 like

@joasahacker
@Data_ls_Life YES
3 likes

@denismagda
@Data_ls_Life I’l check it out. Thanks for sharing
1 like

@dipankarsarkar
Sounds great!
1 like

@flugelduvel
Classic federation. Works well if query can be pushed down and cardinality of fetched data is small. Will be painfull as soon as there is a big cross-database join or so.
1 like

@tobias_petry
> 4. pgduck_server delegates execution to DuckDB, which queries the lakehouse (reusing cached data if available). How does it reuse cached data? Did you setup a file-based cache for the lakehouse data?
1 like

@Mr_D_V_D
can we see the implementation of this so we understand the actual setup

@larshansen
So compared to using DuckLake directly, here the DuckLake tables becomes first-class Postgres citizens? (instead of using special client)

@denismagda
I'm not familiar with DuckLake yet. So, can't compare architectural differences.