← Browse the extensions catalog

pgextwlist

Source README ↗

pgextwlist

PostgreSQL Extension Whitelisting. Upstream documentation.

Follow the quick start to set up extension-update email alerts first, then use the CronJob to install and refresh the catalog. These examples inherit image references and runtime settings from the catalog. The Cluster YAML is an excerpt: replace imageCatalogRef: ... with your catalog reference and keep your existing instance and storage settings.

Supported images

PostgreSQL 18; Debian Trixie and Bookworm; amd64 and arm64 build targets.

Usage

1. Add the pgextwlist extension image to your Cluster

apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: cluster-pgextwlist
spec:
  imageCatalogRef: ...
  postgresql:
    shared_preload_libraries:
    - pgextwlist
    parameters:
      extwlist.extensions: dblink
    extensions:
    - name: pgextwlist

2. Verify operation

Connect with psql and run SHOW extwlist.extensions; to check the configured allowlist.

Operation and privileges

This module has no CREATE EXTENSION artifact. Its preload hook allows non-superusers to install administrator-allowlisted extensions that normally require superuser privileges; PostgreSQL trusted extensions retain their ordinary permissions. The example allowlists dblink, already present in the minimal PostgreSQL image. Optional custom script execution is not configured or supported by this image.

Dependencies and updates

The image contains only the PGDG package server payload and license notices. The matching CNPG minimal image supplies PostgreSQL, libc and its base runtime. Project automation tracks package updates and rebuilds the extension images. Use the catalog maintenance schedule in the quick start to consume published PostgreSQL and extension image updates. Monitor pending SQL extension upgrades and review them separately; SQL versions need not match package versions.

Licenses and ownership

PostgreSQL. Redistribution notices are preserved under /licenses/.