Let Postgres own the Iceberg catalog and delegate analytics to DuckDB.
@denismagda5050 位关注者
28,597 次观看
10 条评论
评论来自 X (Twitter) 上的原帖

@Data_ls_Life
Just use DuckLake
2 个赞

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

@joasahacker
@Data_ls_Life YES
3 个赞

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

@dipankarsarkar
Sounds great!
1 个赞

@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 个赞

@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 个赞

@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.