You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make read_only a server option; Support TYPE 'object_store' servers
Allow CREATE SERVER ... TYPE 'object_store' FOREIGN DATA WRAPPER
iceberg_catalog, mirroring the existing TYPE 'rest' pattern. Each
server can carry its own location_prefix and read_only options,
enabling shared writer/reader topologies where multiple Postgres
instances point at the same S3 path.
Key changes:
- ValidateIcebergCatalogServerDDL now accepts TYPE 'object_store'
(TYPE 'postgres' remains rejected).
- Add IsObjectStoreCatalog() in catalog_type.c, paralleling
IsRestCatalog(); update HasObjectStoreCatalogTableOption to use it
so that tables with catalog='<named_server>' resolve correctly.
- Add ObjectStoreCatalogOptions struct and resolution function that
reads server options with GUC fallback.
- Add read_only as a server-level option (valid for both REST and
object_store servers). Server read_only propagates to all tables
unless overridden; table read_only='false' on a read_only server
is an error.
- Update create_table.c to resolve location_prefix from named
object_store servers instead of requiring the GUC.
- Update IcebergDefaultCatalogCheckHook to accept named object_store
servers.
- Update catalog export SPI query to include tables on named
object_store servers.
0 commit comments