[HN Gopher] Putting DuckDB in Postgres to Query Iceberg
___________________________________________________________________
Putting DuckDB in Postgres to Query Iceberg
Author : philippemnoel
Score : 49 points
Date : 2024-07-11 15:29 UTC (7 hours ago)
(HTM) web link (blog.paradedb.com)
(TXT) w3m dump (blog.paradedb.com)
| mritchie712 wrote:
| The `duckdb_iceberg`[0] extension doesn't support partitioning /
| predicate pushdown. Is that what you're using for pg_lakehouse?
|
| 0 - https://github.com/duckdb/duckdb_iceberg/issues/2
| philippemnoel wrote:
| It is! They (and we) are working on fixing that so that the
| performance for Iceberg gets a lot better
| mritchie712 wrote:
| amazing! are you thinking of submitting a PR to
| duckdb_iceberg? Or an alternative fix?
| philippemnoel wrote:
| It would be to duckdb_iceberg, yes. We're looking to keep
| things in the open-source :)
| rubenfiszel wrote:
| Why not call it pg_duckdb ?
| philippemnoel wrote:
| The first version of it was built using Apache DataFusion and
| we kept the name. We're planning for it to become more than
| "just" DuckDB in Postgres
| chrisjc wrote:
| Interested to hear why you switched from DataFusion?
| wenc wrote:
| It's in the linked article.
| bastawhiz wrote:
| That's the whole point of the article, really.
| chuckhend wrote:
| Congrats to the paradedb team!
| nhudson2367 wrote:
| congrats paradedb team!
| lolive wrote:
| Can you have a single transaction write both to a pg table _and_
| an iceberg table?
| philippemnoel wrote:
| For now, pg_lakehouse is read-only. We are planning to add
| write support and this is a feature we would like to support.
| What is your use case for it?
___________________________________________________________________
(page generated 2024-07-11 23:00 UTC)