Pg_ducklake merge to pg_duckdb

[tcolo]

One question is there a merge planned of pg_ducklake into pg_duckdb?

[YuweiXiao]

Thanks for bringing it up at pg_duckdb! We had a discussion at pg_ducklake relytcloud#16

Actually, pg_ducklake hasn't got feedback from the maintainer here yet and pg_duckdb has been inactive for a month (gentle ping @JelteF ). Would love to discuss about the upstream (the possibility and how to).

[isoctcolo]

I mean it makes sense to integrate ducklake from a logical point - as the postgres extension is the bridge between ducklake and postgresql.

[JelteF]

Sorry, for the radio silence. I've been really busy with other work. I think we'll definitely want official ducklake support in pg_duckdb eventually though. Whether that's through merging pg_ducklake, or going a slightly different approach I'm not sure (I haven't looked at the pg_ducklake code and UX yet).

One thing I'm wondering is whether pg_ducklake could also use the pg_duckdb the extension mechanism that was added for pg_mooncake: #893

Or is that missing some functionality that you need. If so, I can definitely review a small PR that adds a few extra hooks.

[YuweiXiao]

Hey @JelteF , Good to see you back!

pg_ducklake tries to keep changes to the pg_duckdb codebase minimal during development. I've checked all changes, and it looks viable to integrate in a "mooncake" manner. We'll soon work on a PoC for this.

[qsliu2017]

FYI, I just open a PR relytcloud#45 tracking code drift between pg_duckdb and pg_ducklake. Hopefully our work will not conflict with core pg_duckdb.