pg_lake_table

Overview

pg_extension_base auto-loads pg_lake_engine, pg_lake_iceberg, and pg_lake_table in dependency order. Extension SQL/control version is 3.4; source and DEB/RPM package version is 3.4.0.

Version

Build

You can build the RPM / DEB packages for pg_lake using pig build:

pig build pkg pg_lake         # build RPM / DEB packages

Install

You can install pg_lake directly. First, make sure the PGDG and PIGSTY repositories are added and enabled:

pig repo add pgsql -u          # Add repo and update cache

Install the extension using pig or apt/yum/dnf:

• Install
• pig
• dnf
• apt

pig install pg_lake;          # Install for current active PG version

pig ext install -y pg_lake -v 18  # PG 18
pig ext install -y pg_lake -v 17  # PG 17
pig ext install -y pg_lake -v 16  # PG 16

dnf install -y pg_lake_18       # PG 18
dnf install -y pg_lake_17       # PG 17
dnf install -y pg_lake_16       # PG 16

apt install -y postgresql-18-pg-lake   # PG 18
apt install -y postgresql-17-pg-lake   # PG 17
apt install -y postgresql-16-pg-lake   # PG 16

Preload:

shared_preload_libraries = 'pg_extension_base';

Create Extension:

CREATE EXTENSION pg_lake_table CASCADE;  -- requires: btree_gist, pg_lake_engine, pg_lake_iceberg

Usage

Sources:

• Official upstream README

pg_lake_table — Data lake tables and Iceberg tables

The reviewed catalog snapshot records version 3.4, kind preload, and implementation language C. Install and validate the declared extension dependencies first: btree_gist, pg_lake_engine, pg_lake_iceberg. The curated compatibility set is 16,17,18; confirm the exact build against the target server.

CREATE EXTENSION "pg_lake_table";
SELECT extversion
FROM pg_extension
WHERE extname = 'pg_lake_table';

The upstream project is associated with Snowflake; verify its current support, license, packaging, and deployment boundary from the linked source.

The curated lifecycle is active. Pin the reviewed build and verify maintenance status before adoption.

Before production use, review the linked control/SQL or provider documentation, verify privileges and compatibility, and test the actual API and failure behavior on the target PostgreSQL build.