Upstream ducklake feature parity tracker

[qsliu2017]

Overview

This is a tracking issue for upstream ducklake features that pg_ducklake does not yet support. The goal is to reach feature parity with the DuckDB ducklake extension where feasible within PostgreSQL's type system and execution model.

Sub-issues

• feat: schema evolution DDL (RENAME COLUMN, CHANGE TYPE, NOT NULL, DEFAULT, COMMENT) #125 -- Schema Evolution DDL (RENAME COLUMN, CHANGE TYPE, NOT NULL, DEFAULT, COMMENT)
• feat: CREATE/ALTER/DROP VIEW and MACRO in DuckLake catalog #126 -- Views & Macros in DuckLake catalog
• feat: MERGE INTO statement support #127 -- MERGE INTO statement
• feat: file import (COPY FROM and add_data_files) #128 -- File Import (COPY FROM, add_data_files)
• feat: maintenance functions (merge, cleanup, expire) #129 -- Maintenance Functions (merge, cleanup, expire)
• feat: commit metadata and tags (set_commit_message, labels) #130 -- Commit Metadata & Tags
• feat: schema-scoped options and lifecycle settings #131 -- Schema-scoped Options & Lifecycle Settings
• feat: per-file encryption and DuckLake secrets management #132 -- Encryption & Secrets Management

Out of scope (PostgreSQL type system limitations)

These upstream types have no direct PostgreSQL equivalent and are not planned:

• Unsigned integers (UTINYINT, USMALLINT, UINTEGER, UBIGINT, UHUGEINT)
• 128-bit integers (HUGEINT, UHUGEINT)
• Nanosecond-precision temporal types (TIME_NS, TIMESTAMP_NS)