pg_tle

pg_tle : Trusted Language Extensions for PostgreSQL

Overview

Packages

Source

pig build pkg pg_tle;		# build rpm/deb

Install

Make sure PGDG and PIGSTY repo available:

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

Install this extension with pig:

pig install pg_tle;		# install via package name, for the active PG version

pig install pg_tle -v 18;   # install for PG 18
pig install pg_tle -v 17;   # install for PG 17
pig install pg_tle -v 16;   # install for PG 16
pig install pg_tle -v 15;   # install for PG 15
pig install pg_tle -v 14;   # install for PG 14

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_tle';

Create this extension with:

CREATE EXTENSION pg_tle;

Usage

Sources:

• README.md
• pg_tle.control.in
• pg_tle–1.5.2–1.5.3.sql

pg_tle 1.5.3 manages extensions written in trusted PostgreSQL languages. Native installation needs shared preload and a server restart; subsequent TLE definitions are stored in the database. Upstream documents PostgreSQL 12 through 19 Beta 4.

Core Workflow

shared_preload_libraries = 'pg_tle'

CREATE EXTENSION pg_tle;
SELECT pgtle.available_extensions();

Operational Boundaries

pgtle.install_extension() stores an extension definition; CREATE EXTENSION enables it in a database. pgtle.install_update_path() and pgtle.set_default_version() manage versions, while pgtle.available_extensions() lists definitions. pgtle.set_extension_schema() sets schema metadata for a managed extension in 1.5.3, which also tightens identifier validation. TLE administration is restricted through pgtle_admin; executing an installed extension still follows PostgreSQL language and object privileges. Dropping an installed extension and uninstalling its TLE definition are separate operations. Only use trusted extension code and review dependencies and upgrade SQL.