PGEXT.CLOUD – Apache-2.0

h3

Mon, 01 Jan 0001 00:00:00 +0000

pg_h3 : H3 bindings for PostgreSQL

Overview

ID	Extension	Package	Version	Category	License	Language
1530	h3	pg_h3	`4.2.3`	GIS	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d-r	No	Yes	No	Yes	yes	no

Relationships
Need By	h3_postgis
See Also	postgis qdgc pg_geohash pgrouting q3c pg_polyline mobilitydb pg_eviltransform earthdistance pg_sphere
Siblings	h3_postgis

pgdg missing el8.x86.pg17 and el8.x86.pg18

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PGDG	`4.2.3`	18 17 16 15 14	`pg_h3`	-
RPM	PGDG	`4.2.3`	18 17 16 15 14	`h3-pg_$v`	-
DEB	PGDG	`4.2.3`	18 17 16 15 14	`postgresql-$v-h3`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 4.2.3	PIGSTY 4.2.3	PGDG 4.1.3	PGDG 4.1.3	PGDG 4.1.3
el8.aarch64	PGDG 4.2.3	PGDG 4.1.3	PGDG 4.1.3	PGDG 4.1.3	PGDG 4.1.3
el9.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
el9.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
el10.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
el10.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
d12.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
d12.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
d13.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
d13.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u22.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u22.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u24.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u24.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u26.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u26.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3

PG18

Package	Version	OS	ORG	SIZE	File URL
`h3-pg_18`	`4.2.3`	el8.x86_64	pigsty	78.8 KiB	h3-pg_18-4.2.3-1PIGSTY.el8.x86_64.rpm
`h3-pg_18`	`4.2.3`	el8.aarch64	pgdg	70.5 KiB	h3-pg_18-4.2.3-1PGDG.rhel8.aarch64.rpm
`h3-pg_18`	`4.2.3`	el9.x86_64	pgdg	72.4 KiB	h3-pg_18-4.2.3-4PGDG.rhel9.8.x86_64.rpm
`h3-pg_18`	`4.2.3`	el9.x86_64	pgdg	72.6 KiB	h3-pg_18-4.2.3-1PGDG.rhel9.x86_64.rpm
`h3-pg_18`	`4.2.3`	el9.aarch64	pgdg	71.1 KiB	h3-pg_18-4.2.3-4PGDG.rhel9.8.aarch64.rpm
`h3-pg_18`	`4.2.3`	el9.aarch64	pgdg	70.7 KiB	h3-pg_18-4.2.3-1PGDG.rhel9.aarch64.rpm
`h3-pg_18`	`4.2.3`	el10.x86_64	pgdg	73.2 KiB	h3-pg_18-4.2.3-4PGDG.rhel10.2.x86_64.rpm
`h3-pg_18`	`4.2.3`	el10.x86_64	pgdg	73.2 KiB	h3-pg_18-4.2.3-1PGDG.rhel10.x86_64.rpm
`h3-pg_18`	`4.2.3`	el10.aarch64	pgdg	72.4 KiB	h3-pg_18-4.2.3-4PGDG.rhel10.2.aarch64.rpm
`h3-pg_18`	`4.2.3`	el10.aarch64	pgdg	72.6 KiB	h3-pg_18-4.2.3-1PGDG.rhel10.aarch64.rpm
`postgresql-18-h3`	`4.2.3`	d12.x86_64	pgdg	52.8 KiB	postgresql-18-h3_4.2.3-4.pgdg12+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	d12.x86_64	pgdg	52.7 KiB	postgresql-18-h3_4.2.3-3.pgdg12+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-18-h3_4.2.3-4.pgdg12+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-18-h3_4.2.3-3.pgdg12+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	d13.x86_64	pgdg	53.0 KiB	postgresql-18-h3_4.2.3-4.pgdg13+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	d13.x86_64	pgdg	52.9 KiB	postgresql-18-h3_4.2.3-3.pgdg13+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	d13.aarch64	pgdg	51.6 KiB	postgresql-18-h3_4.2.3-4.pgdg13+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	d13.aarch64	pgdg	51.4 KiB	postgresql-18-h3_4.2.3-3.pgdg13+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	u22.x86_64	pgdg	48.8 KiB	postgresql-18-h3_4.2.3-4.pgdg22.04+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	u22.x86_64	pgdg	48.6 KiB	postgresql-18-h3_4.2.3-3.pgdg22.04+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	u22.aarch64	pgdg	46.6 KiB	postgresql-18-h3_4.2.3-4.pgdg22.04+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	u22.aarch64	pgdg	46.6 KiB	postgresql-18-h3_4.2.3-3.pgdg22.04+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	u24.x86_64	pgdg	48.6 KiB	postgresql-18-h3_4.2.3-4.pgdg24.04+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	u24.x86_64	pgdg	48.6 KiB	postgresql-18-h3_4.2.3-3.pgdg24.04+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	u24.aarch64	pgdg	47.2 KiB	postgresql-18-h3_4.2.3-4.pgdg24.04+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	u24.aarch64	pgdg	47.2 KiB	postgresql-18-h3_4.2.3-3.pgdg24.04+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	u26.x86_64	pgdg	49.5 KiB	postgresql-18-h3_4.2.3-4.pgdg26.04+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	u26.x86_64	pgdg	49.4 KiB	postgresql-18-h3_4.2.3-3.pgdg26.04+1_amd64.deb
`postgresql-18-h3`	`4.2.3`	u26.aarch64	pgdg	47.9 KiB	postgresql-18-h3_4.2.3-4.pgdg26.04+1_arm64.deb
`postgresql-18-h3`	`4.2.3`	u26.aarch64	pgdg	47.8 KiB	postgresql-18-h3_4.2.3-3.pgdg26.04+1_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`h3-pg_17`	`4.2.3`	el8.x86_64	pigsty	78.8 KiB	h3-pg_17-4.2.3-1PIGSTY.el8.x86_64.rpm
`h3-pg_17`	`4.1.3`	el8.aarch64	pgdg	63.8 KiB	h3-pg_17-4.1.3-3PGDG.rhel8.aarch64.rpm
`h3-pg_17`	`4.2.3`	el9.x86_64	pgdg	72.4 KiB	h3-pg_17-4.2.3-4PGDG.rhel9.8.x86_64.rpm
`h3-pg_17`	`4.1.3`	el9.x86_64	pgdg	65.8 KiB	h3-pg_17-4.1.3-3PGDG.rhel9.x86_64.rpm
`h3-pg_17`	`4.2.3`	el9.aarch64	pgdg	71.0 KiB	h3-pg_17-4.2.3-4PGDG.rhel9.8.aarch64.rpm
`h3-pg_17`	`4.1.3`	el9.aarch64	pgdg	64.3 KiB	h3-pg_17-4.1.3-3PGDG.rhel9.aarch64.rpm
`h3-pg_17`	`4.2.3`	el10.x86_64	pgdg	72.9 KiB	h3-pg_17-4.2.3-4PGDG.rhel10.2.x86_64.rpm
`h3-pg_17`	`4.2.2`	el10.x86_64	pgdg	71.7 KiB	h3-pg_17-4.2.2-1PGDG.rhel10.x86_64.rpm
`h3-pg_17`	`4.2.3`	el10.aarch64	pgdg	72.4 KiB	h3-pg_17-4.2.3-4PGDG.rhel10.2.aarch64.rpm
`h3-pg_17`	`4.2.2`	el10.aarch64	pgdg	71.0 KiB	h3-pg_17-4.2.2-1PGDG.rhel10.aarch64.rpm
`postgresql-17-h3`	`4.2.3`	d12.x86_64	pgdg	52.7 KiB	postgresql-17-h3_4.2.3-4.pgdg12+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	d12.x86_64	pgdg	52.7 KiB	postgresql-17-h3_4.2.3-3.pgdg12+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-17-h3_4.2.3-4.pgdg12+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	d12.aarch64	pgdg	50.7 KiB	postgresql-17-h3_4.2.3-3.pgdg12+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	d13.x86_64	pgdg	53.1 KiB	postgresql-17-h3_4.2.3-4.pgdg13+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	d13.x86_64	pgdg	52.9 KiB	postgresql-17-h3_4.2.3-3.pgdg13+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	d13.aarch64	pgdg	51.5 KiB	postgresql-17-h3_4.2.3-4.pgdg13+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	d13.aarch64	pgdg	51.5 KiB	postgresql-17-h3_4.2.3-3.pgdg13+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	u22.x86_64	pgdg	48.6 KiB	postgresql-17-h3_4.2.3-4.pgdg22.04+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	u22.x86_64	pgdg	48.6 KiB	postgresql-17-h3_4.2.3-3.pgdg22.04+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	u22.aarch64	pgdg	46.6 KiB	postgresql-17-h3_4.2.3-4.pgdg22.04+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	u22.aarch64	pgdg	46.5 KiB	postgresql-17-h3_4.2.3-3.pgdg22.04+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	u24.x86_64	pgdg	48.6 KiB	postgresql-17-h3_4.2.3-4.pgdg24.04+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	u24.x86_64	pgdg	48.6 KiB	postgresql-17-h3_4.2.3-3.pgdg24.04+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	u24.aarch64	pgdg	47.3 KiB	postgresql-17-h3_4.2.3-4.pgdg24.04+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	u24.aarch64	pgdg	47.3 KiB	postgresql-17-h3_4.2.3-3.pgdg24.04+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	u26.x86_64	pgdg	49.5 KiB	postgresql-17-h3_4.2.3-4.pgdg26.04+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	u26.x86_64	pgdg	49.4 KiB	postgresql-17-h3_4.2.3-3.pgdg26.04+1_amd64.deb
`postgresql-17-h3`	`4.2.3`	u26.aarch64	pgdg	48.0 KiB	postgresql-17-h3_4.2.3-4.pgdg26.04+1_arm64.deb
`postgresql-17-h3`	`4.2.3`	u26.aarch64	pgdg	47.9 KiB	postgresql-17-h3_4.2.3-3.pgdg26.04+1_arm64.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`h3-pg_16`	`4.1.3`	el8.x86_64	pgdg	65.9 KiB	h3-pg_16-4.1.3-1PGDG.rhel8.x86_64.rpm
`h3-pg_16`	`4.1.3`	el8.aarch64	pgdg	63.6 KiB	h3-pg_16-4.1.3-1PGDG.rhel8.aarch64.rpm
`h3-pg_16`	`4.2.3`	el9.x86_64	pgdg	72.6 KiB	h3-pg_16-4.2.3-4PGDG.rhel9.8.x86_64.rpm
`h3-pg_16`	`4.1.3`	el9.x86_64	pgdg	65.4 KiB	h3-pg_16-4.1.3-1PGDG.rhel9.x86_64.rpm
`h3-pg_16`	`4.2.3`	el9.aarch64	pgdg	71.1 KiB	h3-pg_16-4.2.3-4PGDG.rhel9.8.aarch64.rpm
`h3-pg_16`	`4.1.3`	el9.aarch64	pgdg	63.8 KiB	h3-pg_16-4.1.3-1PGDG.rhel9.aarch64.rpm
`h3-pg_16`	`4.2.3`	el10.x86_64	pgdg	72.9 KiB	h3-pg_16-4.2.3-4PGDG.rhel10.2.x86_64.rpm
`h3-pg_16`	`4.2.2`	el10.x86_64	pgdg	71.6 KiB	h3-pg_16-4.2.2-1PGDG.rhel10.x86_64.rpm
`h3-pg_16`	`4.2.3`	el10.aarch64	pgdg	72.5 KiB	h3-pg_16-4.2.3-4PGDG.rhel10.2.aarch64.rpm
`h3-pg_16`	`4.2.2`	el10.aarch64	pgdg	71.0 KiB	h3-pg_16-4.2.2-1PGDG.rhel10.aarch64.rpm
`postgresql-16-h3`	`4.2.3`	d12.x86_64	pgdg	52.8 KiB	postgresql-16-h3_4.2.3-4.pgdg12+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	d12.x86_64	pgdg	52.7 KiB	postgresql-16-h3_4.2.3-3.pgdg12+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-16-h3_4.2.3-4.pgdg12+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-16-h3_4.2.3-3.pgdg12+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	d13.x86_64	pgdg	52.9 KiB	postgresql-16-h3_4.2.3-4.pgdg13+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	d13.x86_64	pgdg	53.0 KiB	postgresql-16-h3_4.2.3-3.pgdg13+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	d13.aarch64	pgdg	51.5 KiB	postgresql-16-h3_4.2.3-4.pgdg13+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	d13.aarch64	pgdg	51.4 KiB	postgresql-16-h3_4.2.3-3.pgdg13+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	u22.x86_64	pgdg	48.7 KiB	postgresql-16-h3_4.2.3-4.pgdg22.04+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	u22.x86_64	pgdg	48.6 KiB	postgresql-16-h3_4.2.3-3.pgdg22.04+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	u22.aarch64	pgdg	46.6 KiB	postgresql-16-h3_4.2.3-4.pgdg22.04+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	u22.aarch64	pgdg	46.6 KiB	postgresql-16-h3_4.2.3-3.pgdg22.04+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	u24.x86_64	pgdg	48.8 KiB	postgresql-16-h3_4.2.3-4.pgdg24.04+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	u24.x86_64	pgdg	48.7 KiB	postgresql-16-h3_4.2.3-3.pgdg24.04+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	u24.aarch64	pgdg	47.3 KiB	postgresql-16-h3_4.2.3-4.pgdg24.04+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	u24.aarch64	pgdg	47.2 KiB	postgresql-16-h3_4.2.3-3.pgdg24.04+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	u26.x86_64	pgdg	49.5 KiB	postgresql-16-h3_4.2.3-4.pgdg26.04+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	u26.x86_64	pgdg	49.4 KiB	postgresql-16-h3_4.2.3-3.pgdg26.04+1_amd64.deb
`postgresql-16-h3`	`4.2.3`	u26.aarch64	pgdg	48.0 KiB	postgresql-16-h3_4.2.3-4.pgdg26.04+1_arm64.deb
`postgresql-16-h3`	`4.2.3`	u26.aarch64	pgdg	47.9 KiB	postgresql-16-h3_4.2.3-3.pgdg26.04+1_arm64.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`h3-pg_15`	`4.1.3`	el8.x86_64	pgdg	65.9 KiB	h3-pg_15-4.1.3-1PGDG.rhel8.x86_64.rpm
`h3-pg_15`	`4.1.3`	el8.aarch64	pgdg	63.6 KiB	h3-pg_15-4.1.3-1PGDG.rhel8.aarch64.rpm
`h3-pg_15`	`4.2.3`	el9.x86_64	pgdg	72.6 KiB	h3-pg_15-4.2.3-4PGDG.rhel9.8.x86_64.rpm
`h3-pg_15`	`4.1.3`	el9.x86_64	pgdg	65.5 KiB	h3-pg_15-4.1.3-1PGDG.rhel9.x86_64.rpm
`h3-pg_15`	`4.2.3`	el9.aarch64	pgdg	71.2 KiB	h3-pg_15-4.2.3-4PGDG.rhel9.8.aarch64.rpm
`h3-pg_15`	`4.1.3`	el9.aarch64	pgdg	63.8 KiB	h3-pg_15-4.1.3-1PGDG.rhel9.aarch64.rpm
`h3-pg_15`	`4.2.3`	el10.x86_64	pgdg	73.0 KiB	h3-pg_15-4.2.3-4PGDG.rhel10.2.x86_64.rpm
`h3-pg_15`	`4.2.2`	el10.x86_64	pgdg	71.6 KiB	h3-pg_15-4.2.2-1PGDG.rhel10.x86_64.rpm
`h3-pg_15`	`4.2.3`	el10.aarch64	pgdg	72.5 KiB	h3-pg_15-4.2.3-4PGDG.rhel10.2.aarch64.rpm
`h3-pg_15`	`4.2.2`	el10.aarch64	pgdg	71.2 KiB	h3-pg_15-4.2.2-1PGDG.rhel10.aarch64.rpm
`postgresql-15-h3`	`4.2.3`	d12.x86_64	pgdg	52.8 KiB	postgresql-15-h3_4.2.3-4.pgdg12+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	d12.x86_64	pgdg	52.7 KiB	postgresql-15-h3_4.2.3-3.pgdg12+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-15-h3_4.2.3-4.pgdg12+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-15-h3_4.2.3-3.pgdg12+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	d13.x86_64	pgdg	52.9 KiB	postgresql-15-h3_4.2.3-4.pgdg13+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	d13.x86_64	pgdg	52.9 KiB	postgresql-15-h3_4.2.3-3.pgdg13+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	d13.aarch64	pgdg	51.4 KiB	postgresql-15-h3_4.2.3-4.pgdg13+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	d13.aarch64	pgdg	51.4 KiB	postgresql-15-h3_4.2.3-3.pgdg13+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	u22.x86_64	pgdg	48.6 KiB	postgresql-15-h3_4.2.3-4.pgdg22.04+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	u22.x86_64	pgdg	48.7 KiB	postgresql-15-h3_4.2.3-3.pgdg22.04+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	u22.aarch64	pgdg	46.6 KiB	postgresql-15-h3_4.2.3-4.pgdg22.04+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	u22.aarch64	pgdg	46.5 KiB	postgresql-15-h3_4.2.3-3.pgdg22.04+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	u24.x86_64	pgdg	48.7 KiB	postgresql-15-h3_4.2.3-4.pgdg24.04+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	u24.x86_64	pgdg	48.6 KiB	postgresql-15-h3_4.2.3-3.pgdg24.04+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	u24.aarch64	pgdg	47.3 KiB	postgresql-15-h3_4.2.3-4.pgdg24.04+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	u24.aarch64	pgdg	47.3 KiB	postgresql-15-h3_4.2.3-3.pgdg24.04+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	u26.x86_64	pgdg	49.5 KiB	postgresql-15-h3_4.2.3-4.pgdg26.04+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	u26.x86_64	pgdg	49.4 KiB	postgresql-15-h3_4.2.3-3.pgdg26.04+1_amd64.deb
`postgresql-15-h3`	`4.2.3`	u26.aarch64	pgdg	47.9 KiB	postgresql-15-h3_4.2.3-4.pgdg26.04+1_arm64.deb
`postgresql-15-h3`	`4.2.3`	u26.aarch64	pgdg	47.9 KiB	postgresql-15-h3_4.2.3-3.pgdg26.04+1_arm64.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`h3-pg_14`	`4.1.3`	el8.x86_64	pgdg	65.9 KiB	h3-pg_14-4.1.3-1PGDG.rhel8.x86_64.rpm
`h3-pg_14`	`4.1.3`	el8.aarch64	pgdg	63.6 KiB	h3-pg_14-4.1.3-1PGDG.rhel8.aarch64.rpm
`h3-pg_14`	`4.2.3`	el9.x86_64	pgdg	72.6 KiB	h3-pg_14-4.2.3-4PGDG.rhel9.8.x86_64.rpm
`h3-pg_14`	`4.1.3`	el9.x86_64	pgdg	65.5 KiB	h3-pg_14-4.1.3-1PGDG.rhel9.x86_64.rpm
`h3-pg_14`	`4.2.3`	el9.aarch64	pgdg	71.2 KiB	h3-pg_14-4.2.3-4PGDG.rhel9.8.aarch64.rpm
`h3-pg_14`	`4.1.3`	el9.aarch64	pgdg	63.7 KiB	h3-pg_14-4.1.3-1PGDG.rhel9.aarch64.rpm
`h3-pg_14`	`4.2.3`	el10.x86_64	pgdg	72.9 KiB	h3-pg_14-4.2.3-4PGDG.rhel10.2.x86_64.rpm
`h3-pg_14`	`4.2.2`	el10.x86_64	pgdg	71.6 KiB	h3-pg_14-4.2.2-1PGDG.rhel10.x86_64.rpm
`h3-pg_14`	`4.2.3`	el10.aarch64	pgdg	72.5 KiB	h3-pg_14-4.2.3-4PGDG.rhel10.2.aarch64.rpm
`h3-pg_14`	`4.2.2`	el10.aarch64	pgdg	71.0 KiB	h3-pg_14-4.2.2-1PGDG.rhel10.aarch64.rpm
`postgresql-14-h3`	`4.2.3`	d12.x86_64	pgdg	52.7 KiB	postgresql-14-h3_4.2.3-4.pgdg12+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	d12.x86_64	pgdg	52.9 KiB	postgresql-14-h3_4.2.3-3.pgdg12+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-14-h3_4.2.3-4.pgdg12+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	d12.aarch64	pgdg	50.8 KiB	postgresql-14-h3_4.2.3-3.pgdg12+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	d13.x86_64	pgdg	53.0 KiB	postgresql-14-h3_4.2.3-4.pgdg13+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	d13.x86_64	pgdg	53.0 KiB	postgresql-14-h3_4.2.3-3.pgdg13+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	d13.aarch64	pgdg	51.5 KiB	postgresql-14-h3_4.2.3-4.pgdg13+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	d13.aarch64	pgdg	51.5 KiB	postgresql-14-h3_4.2.3-3.pgdg13+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	u22.x86_64	pgdg	48.8 KiB	postgresql-14-h3_4.2.3-4.pgdg22.04+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	u22.x86_64	pgdg	48.7 KiB	postgresql-14-h3_4.2.3-3.pgdg22.04+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	u22.aarch64	pgdg	46.6 KiB	postgresql-14-h3_4.2.3-4.pgdg22.04+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	u22.aarch64	pgdg	46.5 KiB	postgresql-14-h3_4.2.3-3.pgdg22.04+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	u24.x86_64	pgdg	48.7 KiB	postgresql-14-h3_4.2.3-4.pgdg24.04+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	u24.x86_64	pgdg	48.7 KiB	postgresql-14-h3_4.2.3-3.pgdg24.04+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	u24.aarch64	pgdg	47.3 KiB	postgresql-14-h3_4.2.3-4.pgdg24.04+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	u24.aarch64	pgdg	47.2 KiB	postgresql-14-h3_4.2.3-3.pgdg24.04+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	u26.x86_64	pgdg	49.5 KiB	postgresql-14-h3_4.2.3-4.pgdg26.04+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	u26.x86_64	pgdg	49.5 KiB	postgresql-14-h3_4.2.3-3.pgdg26.04+1_amd64.deb
`postgresql-14-h3`	`4.2.3`	u26.aarch64	pgdg	47.9 KiB	postgresql-14-h3_4.2.3-4.pgdg26.04+1_arm64.deb
`postgresql-14-h3`	`4.2.3`	u26.aarch64	pgdg	47.8 KiB	postgresql-14-h3_4.2.3-3.pgdg26.04+1_arm64.deb

Source

Repository

github.com/zachasme/h3-pg

Install

Make sure PGDG repo available:

pig repo add pgdg -u    # add pgdg repo and update cache

Install this extension with pig:

pig install pg_h3;		# install via package name, for the active PG version
pig install h3;		# install by extension name, for the current active PG version

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

Create this extension with:

CREATE EXTENSION h3;

Usage

h3-pg: Uber’s H3 Hexagonal Hierarchical Geospatial Indexing System in PostgreSQL

This extension provides PostgreSQL bindings for the H3 Core Library, Uber’s hexagonal hierarchical geospatial indexing system. For the full API reference, see the H3 Documentation.

Generally, all functions have been renamed from camelCase in H3 to snake_case in SQL, prefixed with h3_.

CREATE EXTENSION h3;

SELECT h3_latlng_to_cell(POINT('37.3615593,-122.0553238'), 5);
  h3_latlng_to_cell
-------------------
 85e35e73fffffff

Base Type

The h3index type is an unsigned 64-bit integer representing any H3 object (hexagon, pentagon, directed edge, etc.), displayed as a 16-character hexadecimal string like '8928308280fffff'.

Indexing Functions

These functions find the H3 index containing coordinates, and the center and boundary of H3 indexes.

-- Index a location at a specified resolution (0-15)
SELECT h3_latlng_to_cell(POINT('37.3615593,-122.0553238'), 5);

-- Find the centroid of an index
SELECT h3_cell_to_latlng('85283473fffffff'::h3index);

-- Find the boundary polygon of an index
SELECT h3_cell_to_boundary('85283473fffffff'::h3index);

Use SET h3.extend_antimeridian TO true to extend coordinates when crossing the 180th meridian.

Index Inspection Functions

-- Get resolution of an index (0-15)
SELECT h3_get_resolution('85283473fffffff'::h3index);

-- Get the base cell number
SELECT h3_get_base_cell_number('85283473fffffff'::h3index);

-- Validate an H3 index
SELECT h3_is_valid_cell('85283473fffffff'::h3index);

-- Check if index is a pentagon
SELECT h3_is_pentagon('85283473fffffff'::h3index);

-- Check if resolution has Class III orientation
SELECT h3_is_res_class_iii('85283473fffffff'::h3index);

-- Find all icosahedron faces intersected by an index
SELECT h3_get_icosahedron_faces('85283473fffffff'::h3index);

Grid Traversal Functions

Grid traversal allows finding cells in the vicinity of an origin cell and determining how to traverse the grid from one cell to another.

-- Produce all indices within k distance of origin
SELECT h3_grid_disk('85283473fffffff'::h3index, 2);

-- Indices with distances from origin
SELECT * FROM h3_grid_disk_distances('85283473fffffff'::h3index, 2);

-- Hollow hexagonal ring at distance k
SELECT h3_grid_ring_unsafe('85283473fffffff'::h3index, 1);

-- Line of indexes between two cells (inclusive)
SELECT h3_grid_path_cells('85283473fffffff'::h3index, '8528342bfffffff'::h3index);

-- Grid distance between two indices
SELECT h3_grid_distance('85283473fffffff'::h3index, '8528342bfffffff'::h3index);

-- Local IJ coordinates
SELECT h3_cell_to_local_ij('85283473fffffff'::h3index, '8528342bfffffff'::h3index);
SELECT h3_local_ij_to_cell('85283473fffffff'::h3index, POINT(0,0));

Hierarchical Grid Functions

Move between resolutions in the H3 grid system to produce parent (coarser) or children (finer) cells.

-- Get parent cell at a coarser resolution
SELECT h3_cell_to_parent('85283473fffffff'::h3index, 3);

-- Get all children at a finer resolution
SELECT h3_cell_to_children('85283473fffffff'::h3index, 7);

-- Get center child at a finer resolution
SELECT h3_cell_to_center_child('85283473fffffff'::h3index, 7);

-- Compact an array of cells
SELECT h3_compact_cells(ARRAY['85283473fffffff'::h3index, '85283477fffffff'::h3index]);

-- Uncompact to a target resolution
SELECT h3_uncompact_cells(ARRAY['85283473fffffff'::h3index], 7);

-- Get position of child within parent's children list
SELECT h3_cell_to_child_pos('872834700ffffff'::h3index, 5);

-- Get child at a specific position
SELECT h3_child_pos_to_cell(0, '85283473fffffff'::h3index, 7);

Region Functions

Convert H3 indexes to and from polygonal areas.

-- Fill a polygon with hexagons at a given resolution
SELECT h3_polygon_to_cells(
    '((37.7,-122.5),(37.8,-122.5),(37.8,-122.4),(37.7,-122.4))'::polygon,
    NULL::polygon[],
    5
);

-- Get the outline polygon(s) of a set of hexagons
SELECT * FROM h3_cells_to_multi_polygon(
    ARRAY['85283473fffffff'::h3index, '85283477fffffff'::h3index]
);

Unidirectional Edge Functions

Encode directed edges from one cell to a neighboring cell.

-- Check if two cells are neighbors
SELECT h3_are_neighbor_cells('85283473fffffff'::h3index, '85283477fffffff'::h3index);

-- Get directed edge between neighbors
SELECT h3_cells_to_directed_edge('85283473fffffff'::h3index, '85283477fffffff'::h3index);

-- Validate an edge
SELECT h3_is_valid_directed_edge(edge) FROM ...;

-- Get origin and destination from edge
SELECT h3_get_directed_edge_origin(edge);
SELECT h3_get_directed_edge_destination(edge);

-- Get both as a record
SELECT * FROM h3_directed_edge_to_cells(edge);

-- All edges originating from a cell
SELECT h3_origin_to_directed_edges('85283473fffffff'::h3index);

-- Edge boundary coordinates
SELECT h3_directed_edge_to_boundary(edge);

Vertex Functions

-- Get a single vertex of a cell
SELECT h3_cell_to_vertex('85283473fffffff'::h3index, 0);

-- Get all vertexes of a cell
SELECT h3_cell_to_vertexes('85283473fffffff'::h3index);

-- Get geocoordinates of a vertex
SELECT h3_vertex_to_latlng(vertex);

-- Validate a vertex
SELECT h3_is_valid_vertex(vertex);

Miscellaneous Functions

-- Great circle distance between two points (km, m, or rads)
SELECT h3_great_circle_distance(POINT(37.7,-122.5), POINT(40.7,-74.0), 'km');

-- Average hexagon area at a resolution
SELECT h3_get_hexagon_area_avg(5, 'km^2');

-- Exact area of a specific cell
SELECT h3_cell_area('85283473fffffff'::h3index, 'km^2');

-- Average edge length at a resolution
SELECT h3_get_hexagon_edge_length_avg(5, 'km');

-- Exact edge length
SELECT h3_edge_length(edge, 'km');

-- Number of unique cells at a resolution
SELECT h3_get_num_cells(5);

-- All 122 resolution-0 cells
SELECT h3_get_res_0_cells();

-- All pentagons at a resolution
SELECT h3_get_pentagons(5);

Operators

-- Grid distance operator
SELECT '85283473fffffff'::h3index <-> '8528342bfffffff'::h3index;

-- B-tree equality / inequality
SELECT a = b, a <> b FROM ...;

-- R-tree spatial operators
SELECT a && b  -- intersects
SELECT a @> b  -- contains
SELECT a <@ b  -- contained by

SP-GiST Index (Experimental)

CREATE INDEX spgist_idx ON h3_data USING spgist(hex h3index_ops_experimental);

Type Casts

-- H3 index to/from bigint
SELECT '85283473fffffff'::h3index::bigint;
SELECT 599686042433355775::bigint::h3index;

-- H3 index to point
SELECT '85283473fffffff'::h3index::point;

PostGIS Integration

The GEOMETRY data passed to h3-pg PostGIS functions should be in SRID 4326. Using other SRIDs (e.g. 3857) can result in errors or invalid data.

PostGIS integration requires the companion h3_postgis extension:

CREATE EXTENSION h3_postgis CASCADE;

-- Index a PostGIS geometry at a resolution
SELECT h3_latlng_to_cell(geom, 9) FROM points;

-- Convert H3 cell to PostGIS geometry/geography
SELECT h3_cell_to_geometry('85283473fffffff'::h3index);
SELECT h3_cell_to_geography('85283473fffffff'::h3index);

-- Cell boundary as PostGIS geometry (splits at antimeridian)
SELECT h3_cell_to_boundary_geometry('85283473fffffff'::h3index);

-- Fill PostGIS polygon with H3 cells
SELECT h3_polygon_to_cells(geom, 7) FROM polygons;

-- Convert H3 cells back to PostGIS multipolygon
SELECT h3_cells_to_multi_polygon_geometry(ARRAY['85283473fffffff'::h3index]);

-- PostGIS indexing operators
SELECT geom @ 9 FROM points;  -- geometry @ resolution

Raster Processing

For continuous raster data (temperature, elevation, etc.), summarize pixel values within H3 cells:

SELECT
    (summary).h3 AS h3,
    (h3_raster_summary_stats_agg((summary).stats)).*
FROM (
    SELECT h3_raster_summary(rast, 8) AS summary
    FROM rasters
) t
GROUP BY 1;

For discrete/classified raster data (land cover, land use), aggregate class statistics per H3 cell:

SELECT
    h3,
    jsonb_object_agg(
        concat('class_', val::text),
        h3_raster_class_summary_item_to_jsonb(item)
        ORDER BY val
    ) AS summary
FROM (
    SELECT h3, val, h3_raster_class_summary_item_agg(summary) AS item
    FROM rasters, h3_raster_class_summary(rast, 8)
    GROUP BY 1, 2
) t
GROUP BY 1;

Raster summary methods: h3_raster_summary (auto-selects), h3_raster_summary_clip (clips by cell geometry), h3_raster_summary_centroids (groups by pixel centroid), h3_raster_summary_subpixel (for sub-pixel H3 cells). The same variants exist for class summaries.

h3_postgis

Mon, 01 Jan 0001 00:00:00 +0000

pg_h3 : H3 PostGIS integration

Overview

ID	Extension	Package	Version	Category	License	Language
1531	h3_postgis	pg_h3	`4.2.3`	GIS	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d-r	No	Yes	No	Yes	yes	no

Relationships
Requires	h3 postgis postgis_raster
See Also	postgis qdgc pg_geohash pgrouting q3c pg_polyline pg_eviltransform earthdistance mobilitydb
Siblings	h3

pgdg missing el8.x86.pg17 and el8.x86.pg18

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PGDG	`4.2.3`	18 17 16 15 14	`pg_h3`	`h3`, `postgis`, `postgis_raster`
RPM	PGDG	`4.2.3`	18 17 16 15 14	`h3-pg_$v`	-
DEB	PGDG	`4.2.3`	18 17 16 15 14	`postgresql-$v-h3`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 4.2.3	PIGSTY 4.2.3	PGDG 4.1.3	PGDG 4.1.3	PGDG 4.1.3
el8.aarch64	PGDG 4.2.3	PGDG 4.1.3	PGDG 4.1.3	PGDG 4.1.3	PGDG 4.1.3
el9.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
el9.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
el10.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
el10.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
d12.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
d12.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
d13.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
d13.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u22.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u22.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u24.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u24.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u26.x86_64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3
u26.aarch64	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3	PGDG 4.2.3

Source

Repository

github.com/zachasme/h3-pg

Install

Make sure PGDG repo available:

pig repo add pgdg -u    # add pgdg repo and update cache

Install this extension with pig:

pig install pg_h3;		# install via package name, for the active PG version
pig install h3_postgis;		# install by extension name, for the current active PG version

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

Create this extension with:

CREATE EXTENSION h3_postgis CASCADE; -- requires h3, postgis, postgis_raster

Usage

h3_postgis: PostGIS integration for H3

h3_postgis is a bridge extension that integrates the H3 hexagonal hierarchical spatial index with PostGIS. It enables conversion between H3 indexes and PostGIS geometry types.

CREATE EXTENSION h3_postgis CASCADE;

This extension requires both h3 and postgis to be installed. It provides functions to convert between H3 cell indexes and PostGIS geometries, enabling spatial queries that combine H3’s hexagonal grid system with PostGIS’s spatial capabilities.

Key Functions

-- Convert a PostGIS point to an H3 cell index
SELECT h3_latlng_to_cell(ST_MakePoint(-73.985, 40.748)::point, 9);

-- Get the boundary of an H3 cell as a PostGIS geometry
SELECT h3_cell_to_boundary_geometry('892a1008003ffff'::h3index);

-- Convert H3 cells to PostGIS polygons for visualization
SELECT h3_cell_to_geometry('892a1008003ffff'::h3index);

qdgc

Mon, 01 Jan 0001 00:00:00 +0000

qdgc : Encode, decode, navigate, and fill Extended Quarter Degree Grid Cell codes in pure SQL.

Overview

ID	Extension	Package	Version	Category	License	Language
1700	qdgc	qdgc	`0.1.0`	GIS	Apache-2.0	SQL

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
----dtr	No	No	No	Yes	yes	yes

Relationships
Need By	qdgc_postgis
See Also	h3 pgrouting pg_geohash q3c postgis_topology pg_polyline pg_eviltransform mobilitydb earthdistance pointcloud
Siblings	qdgc_postgis

PGXN distribution qdgc also ships qdgc_postgis; the GitHub v0.1.0 tag belongs to qdgc-py and is not this PGXN release.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.1.0`	18 17 16 15 14	`qdgc`	-
RPM	PIGSTY	`0.1.0`	18 17 16 15 14	`qdgc_$v`	-
DEB	PIGSTY	`0.1.0`	18 17 16 15 14	`postgresql-$v-qdgc`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el8.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el9.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el9.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el10.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el10.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
d12.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
d12.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
d13.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
d13.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u22.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u22.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u24.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u24.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u26.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u26.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0

PG18

Package	Version	OS	ORG	SIZE	File URL
`qdgc_18`	`0.1.0`	el8.x86_64	pigsty	25.0 KiB	qdgc_18-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_18`	`0.1.0`	el8.aarch64	pigsty	24.9 KiB	qdgc_18-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_18`	`0.1.0`	el9.x86_64	pigsty	24.5 KiB	qdgc_18-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_18`	`0.1.0`	el9.aarch64	pigsty	24.5 KiB	qdgc_18-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_18`	`0.1.0`	el10.x86_64	pigsty	24.7 KiB	qdgc_18-0.1.0-1PIGSTY.el10.noarch.rpm
`qdgc_18`	`0.1.0`	el10.aarch64	pigsty	24.6 KiB	qdgc_18-0.1.0-1PIGSTY.el10.noarch.rpm
`postgresql-18-qdgc`	`0.1.0`	d12.x86_64	pigsty	16.1 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-18-qdgc`	`0.1.0`	d12.aarch64	pigsty	16.1 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-18-qdgc`	`0.1.0`	d13.x86_64	pigsty	16.1 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-18-qdgc`	`0.1.0`	d13.aarch64	pigsty	16.1 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-18-qdgc`	`0.1.0`	u22.x86_64	pigsty	16.5 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-18-qdgc`	`0.1.0`	u22.aarch64	pigsty	16.5 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-18-qdgc`	`0.1.0`	u24.x86_64	pigsty	16.5 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-18-qdgc`	`0.1.0`	u24.aarch64	pigsty	16.5 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-18-qdgc`	`0.1.0`	u26.x86_64	pigsty	16.5 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~resolute_all.deb
`postgresql-18-qdgc`	`0.1.0`	u26.aarch64	pigsty	16.5 KiB	postgresql-18-qdgc_0.1.0-1PIGSTY~resolute_all.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`qdgc_17`	`0.1.0`	el8.x86_64	pigsty	25.0 KiB	qdgc_17-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_17`	`0.1.0`	el8.aarch64	pigsty	24.9 KiB	qdgc_17-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_17`	`0.1.0`	el9.x86_64	pigsty	24.5 KiB	qdgc_17-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_17`	`0.1.0`	el9.aarch64	pigsty	24.5 KiB	qdgc_17-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_17`	`0.1.0`	el10.x86_64	pigsty	24.7 KiB	qdgc_17-0.1.0-1PIGSTY.el10.noarch.rpm
`qdgc_17`	`0.1.0`	el10.aarch64	pigsty	24.6 KiB	qdgc_17-0.1.0-1PIGSTY.el10.noarch.rpm
`postgresql-17-qdgc`	`0.1.0`	d12.x86_64	pigsty	16.1 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-17-qdgc`	`0.1.0`	d12.aarch64	pigsty	16.1 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-17-qdgc`	`0.1.0`	d13.x86_64	pigsty	16.1 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-17-qdgc`	`0.1.0`	d13.aarch64	pigsty	16.1 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-17-qdgc`	`0.1.0`	u22.x86_64	pigsty	16.5 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-17-qdgc`	`0.1.0`	u22.aarch64	pigsty	16.5 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-17-qdgc`	`0.1.0`	u24.x86_64	pigsty	16.5 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-17-qdgc`	`0.1.0`	u24.aarch64	pigsty	16.5 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-17-qdgc`	`0.1.0`	u26.x86_64	pigsty	16.5 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~resolute_all.deb
`postgresql-17-qdgc`	`0.1.0`	u26.aarch64	pigsty	16.5 KiB	postgresql-17-qdgc_0.1.0-1PIGSTY~resolute_all.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`qdgc_16`	`0.1.0`	el8.x86_64	pigsty	25.0 KiB	qdgc_16-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_16`	`0.1.0`	el8.aarch64	pigsty	24.9 KiB	qdgc_16-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_16`	`0.1.0`	el9.x86_64	pigsty	24.5 KiB	qdgc_16-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_16`	`0.1.0`	el9.aarch64	pigsty	24.5 KiB	qdgc_16-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_16`	`0.1.0`	el10.x86_64	pigsty	24.7 KiB	qdgc_16-0.1.0-1PIGSTY.el10.noarch.rpm
`qdgc_16`	`0.1.0`	el10.aarch64	pigsty	24.6 KiB	qdgc_16-0.1.0-1PIGSTY.el10.noarch.rpm
`postgresql-16-qdgc`	`0.1.0`	d12.x86_64	pigsty	16.1 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-16-qdgc`	`0.1.0`	d12.aarch64	pigsty	16.1 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-16-qdgc`	`0.1.0`	d13.x86_64	pigsty	16.1 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-16-qdgc`	`0.1.0`	d13.aarch64	pigsty	16.1 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-16-qdgc`	`0.1.0`	u22.x86_64	pigsty	16.5 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-16-qdgc`	`0.1.0`	u22.aarch64	pigsty	16.5 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-16-qdgc`	`0.1.0`	u24.x86_64	pigsty	16.5 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-16-qdgc`	`0.1.0`	u24.aarch64	pigsty	16.5 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-16-qdgc`	`0.1.0`	u26.x86_64	pigsty	16.5 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~resolute_all.deb
`postgresql-16-qdgc`	`0.1.0`	u26.aarch64	pigsty	16.5 KiB	postgresql-16-qdgc_0.1.0-1PIGSTY~resolute_all.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`qdgc_15`	`0.1.0`	el8.x86_64	pigsty	25.0 KiB	qdgc_15-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_15`	`0.1.0`	el8.aarch64	pigsty	24.9 KiB	qdgc_15-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_15`	`0.1.0`	el9.x86_64	pigsty	24.5 KiB	qdgc_15-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_15`	`0.1.0`	el9.aarch64	pigsty	24.5 KiB	qdgc_15-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_15`	`0.1.0`	el10.x86_64	pigsty	24.7 KiB	qdgc_15-0.1.0-1PIGSTY.el10.noarch.rpm
`qdgc_15`	`0.1.0`	el10.aarch64	pigsty	24.6 KiB	qdgc_15-0.1.0-1PIGSTY.el10.noarch.rpm
`postgresql-15-qdgc`	`0.1.0`	d12.x86_64	pigsty	16.1 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-15-qdgc`	`0.1.0`	d12.aarch64	pigsty	16.1 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-15-qdgc`	`0.1.0`	d13.x86_64	pigsty	16.1 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-15-qdgc`	`0.1.0`	d13.aarch64	pigsty	16.1 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-15-qdgc`	`0.1.0`	u22.x86_64	pigsty	16.5 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-15-qdgc`	`0.1.0`	u22.aarch64	pigsty	16.5 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-15-qdgc`	`0.1.0`	u24.x86_64	pigsty	16.5 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-15-qdgc`	`0.1.0`	u24.aarch64	pigsty	16.5 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-15-qdgc`	`0.1.0`	u26.x86_64	pigsty	16.5 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~resolute_all.deb
`postgresql-15-qdgc`	`0.1.0`	u26.aarch64	pigsty	16.5 KiB	postgresql-15-qdgc_0.1.0-1PIGSTY~resolute_all.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`qdgc_14`	`0.1.0`	el8.x86_64	pigsty	25.0 KiB	qdgc_14-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_14`	`0.1.0`	el8.aarch64	pigsty	24.9 KiB	qdgc_14-0.1.0-1PIGSTY.el8.noarch.rpm
`qdgc_14`	`0.1.0`	el9.x86_64	pigsty	24.5 KiB	qdgc_14-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_14`	`0.1.0`	el9.aarch64	pigsty	24.5 KiB	qdgc_14-0.1.0-1PIGSTY.el9.noarch.rpm
`qdgc_14`	`0.1.0`	el10.x86_64	pigsty	24.7 KiB	qdgc_14-0.1.0-1PIGSTY.el10.noarch.rpm
`qdgc_14`	`0.1.0`	el10.aarch64	pigsty	24.6 KiB	qdgc_14-0.1.0-1PIGSTY.el10.noarch.rpm
`postgresql-14-qdgc`	`0.1.0`	d12.x86_64	pigsty	16.1 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-14-qdgc`	`0.1.0`	d12.aarch64	pigsty	16.1 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~bookworm_all.deb
`postgresql-14-qdgc`	`0.1.0`	d13.x86_64	pigsty	16.1 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-14-qdgc`	`0.1.0`	d13.aarch64	pigsty	16.1 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~trixie_all.deb
`postgresql-14-qdgc`	`0.1.0`	u22.x86_64	pigsty	16.5 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-14-qdgc`	`0.1.0`	u22.aarch64	pigsty	16.5 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~jammy_all.deb
`postgresql-14-qdgc`	`0.1.0`	u24.x86_64	pigsty	16.5 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-14-qdgc`	`0.1.0`	u24.aarch64	pigsty	16.5 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~noble_all.deb
`postgresql-14-qdgc`	`0.1.0`	u26.x86_64	pigsty	16.5 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~resolute_all.deb
`postgresql-14-qdgc`	`0.1.0`	u26.aarch64	pigsty	16.5 KiB	postgresql-14-qdgc_0.1.0-1PIGSTY~resolute_all.deb

Source

Repository

pgxn.org/dist/qdgc/0.1.0/

Source Tarball

qdgc-0.1.0.tar.gz

pig build pkg qdgc;		# 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 qdgc;		# install via package name, for the active PG version

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

Create this extension with:

CREATE EXTENSION qdgc;

Usage

Sources:

qdgc 0.1.0 is the trusted, relocatable, pure-SQL core of the QDGC extension family. It encodes longitude and latitude as Extended Quarter Degree Grid Cell codes, decodes their bounds, navigates the prefix hierarchy, reports level metrics, and fills longitude/latitude bounding boxes. It has no PostGIS or compiled-library dependency; geometry, geography, and polygon-fill operations belong to the companion qdgc_postgis extension.

Core Workflow

CREATE EXTENSION qdgc;

-- qdgc_encode uses (longitude, latitude, level).
SELECT qdgc_encode(31.4, 2.7, 5);
-- E031N02ADBAC

-- The h3-style alias reverses the coordinate arguments.
SELECT qdgc_latlng_to_cell(2.7, 31.4, 5);

SELECT *
FROM qdgc_cell_to_bounds('E031N02ADBAC');

SELECT qdgc_cell_to_parent('E031N02ADBAC', 3);
SELECT * FROM qdgc_cell_to_children('E031N02AD', 5);

QDGC hierarchy is encoded directly in the text: a child code begins with its parent code. That makes prefix filtering useful for rollups and descendant lookups:

CREATE TABLE observations (
    id bigint GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
    qdgc_code text NOT NULL
);

CREATE INDEX observations_qdgc_idx ON observations (qdgc_code);

SELECT qdgc_cell_to_parent(qdgc_code, 3) AS level_3_cell,
       count(*)
FROM observations
GROUP BY 1;

SELECT *
FROM observations
WHERE qdgc_code LIKE 'E031N02AB%';

Bounding Boxes and Level Metrics

The core extension can enumerate rectangular coverage without PostGIS. Pass min_lon > max_lon for a box that crosses the antimeridian.

SELECT qdgc_bbox_cell_count(30.0, 1.0, 32.0, 3.0, 7);

SELECT *
FROM qdgc_bbox_to_cells(30.0, 1.0, 32.0, 3.0, 7);

SELECT qdgc_level_degrees(7);
SELECT qdgc_get_num_cells(7);
SELECT qdgc_average_cell_area(7, 2.0, 'km^2');
SELECT qdgc_version();

qdgc_average_cell_area is a spherical estimate. Use qdgc_cell_area_km2 from qdgc_postgis when a cell-specific WGS84 spheroid measurement is required.

Important Objects

qdgc_encode(lon, lat, level) and qdgc_latlng_to_cell(lat, lng, level) create codes; the argument order is intentionally different.
qdgc_is_valid_cell, qdgc_get_level, qdgc_cell_to_bounds, qdgc_cell_to_lonlat, and qdgc_cell_to_latlng inspect or decode a code.
qdgc_cell_to_parent and qdgc_cell_to_children navigate the four-way prefix hierarchy.
qdgc_bbox_to_cells enumerates cells meeting a bounding box, while qdgc_bbox_cell_count calculates the count without materializing the set.
qdgc_level_degrees, qdgc_get_num_cells, and qdgc_average_cell_area report grid-level metrics.

Operational Notes

Upstream requires PostgreSQL 13 or newer and tests PostgreSQL 13 through 17. PostgreSQL 18 is not part of the published 0.1.0 test matrix.
The control file sets trusted = true and relocatable = true. No shared_preload_libraries, LOAD, server restart, or native library is required.
Relocatable functions call one another by unqualified name. Install qdgc into a schema on the active search_path; the default public schema satisfies this boundary.
Coordinates are longitude/latitude degrees. qdgc_encode takes longitude first, while qdgc_latlng_to_cell takes latitude first.
Result cardinality grows by four for every additional child level. Count a bounding-box fill before materializing it, and avoid requesting deep descendants without a deliberate result-size bound.

qdgc_postgis

Mon, 01 Jan 0001 00:00:00 +0000

qdgc : Add PostGIS geometry and geography bindings plus area-to-cell fills for QDGC.

Overview

ID	Extension	Package	Version	Category	License	Language
1710	qdgc_postgis	qdgc	`0.1.0`	GIS	Apache-2.0	SQL

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
----d-r	No	No	No	Yes	yes	no

Relationships
Requires	qdgc postgis
See Also	postgis h3 pg_geohash pgrouting q3c pg_polyline pg_eviltransform earthdistance mobilitydb
Siblings	qdgc

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.1.0`	18 17 16 15 14	`qdgc`	`qdgc`, `postgis`
RPM	PIGSTY	`0.1.0`	18 17 16 15 14	`qdgc_$v`	-
DEB	PIGSTY	`0.1.0`	18 17 16 15 14	`postgresql-$v-qdgc`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el8.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el9.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el9.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el10.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
el10.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
d12.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
d12.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
d13.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
d13.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u22.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u22.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u24.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u24.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u26.x86_64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0
u26.aarch64	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0	PIGSTY 0.1.0

Source

Repository

pgxn.org/dist/qdgc/0.1.0/

Source Tarball

qdgc-0.1.0.tar.gz

pig build pkg qdgc;		# 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 qdgc;		# install via package name, for the active PG version
pig install qdgc_postgis;		# install by extension name, for the current active PG version

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

Create this extension with:

CREATE EXTENSION qdgc_postgis CASCADE; -- requires qdgc, postgis

Usage

Sources:

qdgc_postgis 0.1.0 is the PostGIS companion to the pure-SQL qdgc core. It converts QDGC cells to and from PostGIS points and polygons, measures cell area on the WGS84 spheroid, and fills arbitrary geometries with QDGC cells. The extension requires both qdgc and postgis; it does not replace either one.

Core Workflow

CREATE EXTENSION postgis;
CREATE EXTENSION qdgc;
CREATE EXTENSION qdgc_postgis;

SELECT qdgc_latlng_to_cell(
    ST_SetSRID(ST_MakePoint(31.4, 2.7), 4326),
    5
);

SELECT qdgc_cell_to_geometry('E031N02ADBAC');
SELECT qdgc_cell_to_boundary_geometry('E031N02ADBAC');
SELECT qdgc_cell_area_km2('E031N02ADBAC');

The point overload transforms geometry with a nonzero, non-4326 SRID to EPSG:4326. An SRID of zero is assumed to already contain longitude and latitude.

Fill an Area of Interest

Estimate the result size before producing a deep fill:

WITH area AS (
    SELECT ST_GeomFromText(
        'POLYGON((31.0 2.0, 31.5 2.0, 31.5 2.5, 31.0 2.5, 31.0 2.0))',
        4326
    ) AS geom
)
SELECT qdgc_estimate_cell_count(geom, 7)
FROM area;

WITH area AS (
    SELECT ST_GeomFromText(
        'POLYGON((31.0 2.0, 31.5 2.0, 31.5 2.5, 31.0 2.5, 31.0 2.0))',
        4326
    ) AS geom
)
SELECT cell
FROM area
CROSS JOIN LATERAL qdgc_polygon_to_cells(
    geom,
    7,
    'intersects'
) AS cell;

The predicate can be:

intersects, the default, for cells intersecting the geometry;
centroid, for cells whose center lies inside the geometry;
contains, for cells wholly contained by the geometry.

The implementation descends a pruning quadtree instead of testing every cell in the geometry’s full envelope. Multi-part geometries are filled per part and their cell sets are combined.

Important Objects

qdgc_latlng_to_cell(geometry, level) and its geography overload encode PostGIS points.
qdgc_cell_to_geometry and qdgc_cell_to_geography return the cell centroid.
qdgc_cell_to_boundary_geometry and qdgc_cell_to_boundary_geography return the rectangular cell boundary.
qdgc_cell_area_km2 measures the boundary geography on the WGS84 spheroid.
qdgc_polygon_to_cells fills an area using one of the three documented predicates.
qdgc_estimate_cell_count provides a cheap, envelope-capped guard before materializing a fill.

Operational Notes

qdgc_postgis.control declares requires = 'qdgc,postgis' and relocatable = true. Install PostGIS with an appropriately privileged role before delegating use of the companion extension.
No shared_preload_libraries, LOAD, or restart is required. The extension is SQL-only, but its PostGIS dependency includes native code.
Install qdgc, qdgc_postgis, and their callable dependencies into schemas visible on the active search_path, because the relocatable SQL calls functions by unqualified name.
Upstream tests PostgreSQL 13 through 17. Do not infer PostgreSQL 18 support from the absence of compiled code.
Deep area fills can still produce enormous sets even with pruning. Treat qdgc_estimate_cell_count as an operational guard and apply application-specific limits before executing qdgc_polygon_to_cells.

pg_tiktoken

Mon, 01 Jan 0001 00:00:00 +0000

pg_tiktoken : tiktoken tokenizer for use with OpenAI models in postgres

Overview

ID	Extension	Package	Version	Category	License	Language
1870	pg_tiktoken	pg_tiktoken	`0.0.1`	RAG	Apache-2.0	Rust

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d--	No	Yes	No	Yes	no	no

Relationships
See Also	pg_tiktoken_c pg_tokenizer pg_jieba pg_cjk_parser zhparser pg_bigm pgroonga dict_xsyn

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.0.1`	18 17 16 15 14	`pg_tiktoken`	-
RPM	PIGSTY	`0.0.1`	18 17 16 15 14	`pg_tiktoken_$v`	-
DEB	PIGSTY	`0.0.1`	18 17 16 15 14	`postgresql-$v-pg-tiktoken`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
el8.aarch64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
el9.x86_64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
el9.aarch64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
el10.x86_64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
el10.aarch64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
d12.x86_64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
d12.aarch64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
d13.x86_64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
d13.aarch64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
u22.x86_64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
u22.aarch64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
u24.x86_64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
u24.aarch64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
u26.x86_64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1
u26.aarch64	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1	PIGSTY 0.0.1

PG18

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_18`	`0.0.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_18-0.0.1-4PIGSTY.el8.x86_64.rpm
`pg_tiktoken_18`	`0.0.1`	el8.aarch64	pigsty	2.2 MiB	pg_tiktoken_18-0.0.1-4PIGSTY.el8.aarch64.rpm
`pg_tiktoken_18`	`0.0.1`	el9.x86_64	pigsty	2.2 MiB	pg_tiktoken_18-0.0.1-4PIGSTY.el9.x86_64.rpm
`pg_tiktoken_18`	`0.0.1`	el9.aarch64	pigsty	2.2 MiB	pg_tiktoken_18-0.0.1-4PIGSTY.el9.aarch64.rpm
`pg_tiktoken_18`	`0.0.1`	el10.x86_64	pigsty	2.2 MiB	pg_tiktoken_18-0.0.1-4PIGSTY.el10.x86_64.rpm
`pg_tiktoken_18`	`0.0.1`	el10.aarch64	pigsty	2.2 MiB	pg_tiktoken_18-0.0.1-4PIGSTY.el10.aarch64.rpm
`postgresql-18-pg-tiktoken`	`0.0.1`	d12.x86_64	pigsty	1.9 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~bookworm_amd64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	d12.aarch64	pigsty	1.7 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~bookworm_arm64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	d13.x86_64	pigsty	1.9 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~trixie_amd64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	d13.aarch64	pigsty	1.7 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~trixie_arm64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~jammy_amd64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	u22.aarch64	pigsty	2.0 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~jammy_arm64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~noble_amd64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	u24.aarch64	pigsty	2.0 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~noble_arm64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~resolute_amd64.deb
`postgresql-18-pg-tiktoken`	`0.0.1`	u26.aarch64	pigsty	2.0 MiB	postgresql-18-pg-tiktoken_0.0.1-3PIGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_17`	`0.0.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_17-0.0.1-4PIGSTY.el8.x86_64.rpm
`pg_tiktoken_17`	`0.0.1`	el8.aarch64	pigsty	2.2 MiB	pg_tiktoken_17-0.0.1-4PIGSTY.el8.aarch64.rpm
`pg_tiktoken_17`	`0.0.1`	el9.x86_64	pigsty	2.2 MiB	pg_tiktoken_17-0.0.1-4PIGSTY.el9.x86_64.rpm
`pg_tiktoken_17`	`0.0.1`	el9.aarch64	pigsty	2.2 MiB	pg_tiktoken_17-0.0.1-4PIGSTY.el9.aarch64.rpm
`pg_tiktoken_17`	`0.0.1`	el10.x86_64	pigsty	2.2 MiB	pg_tiktoken_17-0.0.1-4PIGSTY.el10.x86_64.rpm
`pg_tiktoken_17`	`0.0.1`	el10.aarch64	pigsty	2.2 MiB	pg_tiktoken_17-0.0.1-4PIGSTY.el10.aarch64.rpm
`postgresql-17-pg-tiktoken`	`0.0.1`	d12.x86_64	pigsty	1.9 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~bookworm_amd64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	d12.aarch64	pigsty	1.7 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~bookworm_arm64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	d13.x86_64	pigsty	1.9 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~trixie_amd64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	d13.aarch64	pigsty	1.7 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~trixie_arm64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~jammy_amd64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	u22.aarch64	pigsty	2.0 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~jammy_arm64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~noble_amd64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	u24.aarch64	pigsty	2.0 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~noble_arm64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~resolute_amd64.deb
`postgresql-17-pg-tiktoken`	`0.0.1`	u26.aarch64	pigsty	2.0 MiB	postgresql-17-pg-tiktoken_0.0.1-3PIGSTY~resolute_arm64.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_16`	`0.0.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_16-0.0.1-4PIGSTY.el8.x86_64.rpm
`pg_tiktoken_16`	`0.0.1`	el8.aarch64	pigsty	2.2 MiB	pg_tiktoken_16-0.0.1-4PIGSTY.el8.aarch64.rpm
`pg_tiktoken_16`	`0.0.1`	el9.x86_64	pigsty	2.2 MiB	pg_tiktoken_16-0.0.1-4PIGSTY.el9.x86_64.rpm
`pg_tiktoken_16`	`0.0.1`	el9.aarch64	pigsty	2.2 MiB	pg_tiktoken_16-0.0.1-4PIGSTY.el9.aarch64.rpm
`pg_tiktoken_16`	`0.0.1`	el10.x86_64	pigsty	2.2 MiB	pg_tiktoken_16-0.0.1-4PIGSTY.el10.x86_64.rpm
`pg_tiktoken_16`	`0.0.1`	el10.aarch64	pigsty	2.2 MiB	pg_tiktoken_16-0.0.1-4PIGSTY.el10.aarch64.rpm
`postgresql-16-pg-tiktoken`	`0.0.1`	d12.x86_64	pigsty	1.9 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~bookworm_amd64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	d12.aarch64	pigsty	1.7 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~bookworm_arm64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	d13.x86_64	pigsty	1.9 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~trixie_amd64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	d13.aarch64	pigsty	1.7 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~trixie_arm64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~jammy_amd64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	u22.aarch64	pigsty	2.0 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~jammy_arm64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~noble_amd64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	u24.aarch64	pigsty	2.0 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~noble_arm64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~resolute_amd64.deb
`postgresql-16-pg-tiktoken`	`0.0.1`	u26.aarch64	pigsty	2.0 MiB	postgresql-16-pg-tiktoken_0.0.1-3PIGSTY~resolute_arm64.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_15`	`0.0.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_15-0.0.1-4PIGSTY.el8.x86_64.rpm
`pg_tiktoken_15`	`0.0.1`	el8.aarch64	pigsty	2.2 MiB	pg_tiktoken_15-0.0.1-4PIGSTY.el8.aarch64.rpm
`pg_tiktoken_15`	`0.0.1`	el9.x86_64	pigsty	2.2 MiB	pg_tiktoken_15-0.0.1-4PIGSTY.el9.x86_64.rpm
`pg_tiktoken_15`	`0.0.1`	el9.aarch64	pigsty	2.2 MiB	pg_tiktoken_15-0.0.1-4PIGSTY.el9.aarch64.rpm
`pg_tiktoken_15`	`0.0.1`	el10.x86_64	pigsty	2.2 MiB	pg_tiktoken_15-0.0.1-4PIGSTY.el10.x86_64.rpm
`pg_tiktoken_15`	`0.0.1`	el10.aarch64	pigsty	2.2 MiB	pg_tiktoken_15-0.0.1-4PIGSTY.el10.aarch64.rpm
`postgresql-15-pg-tiktoken`	`0.0.1`	d12.x86_64	pigsty	1.8 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~bookworm_amd64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	d12.aarch64	pigsty	1.7 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~bookworm_arm64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	d13.x86_64	pigsty	1.8 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~trixie_amd64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	d13.aarch64	pigsty	1.7 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~trixie_arm64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~jammy_amd64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	u22.aarch64	pigsty	2.0 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~jammy_arm64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~noble_amd64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	u24.aarch64	pigsty	2.0 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~noble_arm64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~resolute_amd64.deb
`postgresql-15-pg-tiktoken`	`0.0.1`	u26.aarch64	pigsty	2.0 MiB	postgresql-15-pg-tiktoken_0.0.1-3PIGSTY~resolute_arm64.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_14`	`0.0.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_14-0.0.1-4PIGSTY.el8.x86_64.rpm
`pg_tiktoken_14`	`0.0.1`	el8.aarch64	pigsty	2.2 MiB	pg_tiktoken_14-0.0.1-4PIGSTY.el8.aarch64.rpm
`pg_tiktoken_14`	`0.0.1`	el9.x86_64	pigsty	2.2 MiB	pg_tiktoken_14-0.0.1-4PIGSTY.el9.x86_64.rpm
`pg_tiktoken_14`	`0.0.1`	el9.aarch64	pigsty	2.2 MiB	pg_tiktoken_14-0.0.1-4PIGSTY.el9.aarch64.rpm
`pg_tiktoken_14`	`0.0.1`	el10.x86_64	pigsty	2.2 MiB	pg_tiktoken_14-0.0.1-4PIGSTY.el10.x86_64.rpm
`pg_tiktoken_14`	`0.0.1`	el10.aarch64	pigsty	2.2 MiB	pg_tiktoken_14-0.0.1-4PIGSTY.el10.aarch64.rpm
`postgresql-14-pg-tiktoken`	`0.0.1`	d12.x86_64	pigsty	1.8 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~bookworm_amd64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	d12.aarch64	pigsty	1.7 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~bookworm_arm64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	d13.x86_64	pigsty	1.8 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~trixie_amd64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	d13.aarch64	pigsty	1.7 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~trixie_arm64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~jammy_amd64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	u22.aarch64	pigsty	2.0 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~jammy_arm64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~noble_amd64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	u24.aarch64	pigsty	2.0 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~noble_arm64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~resolute_amd64.deb
`postgresql-14-pg-tiktoken`	`0.0.1`	u26.aarch64	pigsty	2.0 MiB	postgresql-14-pg-tiktoken_0.0.1-3PIGSTY~resolute_arm64.deb

Source

Repository

github.com/kelvich/pg_tiktoken

Source Tarball

pg_tiktoken-0.0.1.tar.gz

pig build pkg pg_tiktoken;		# 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_tiktoken;		# install via package name, for the active PG version

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

Create this extension with:

CREATE EXTENSION pg_tiktoken;

Usage

pg_tiktoken: tiktoken tokenizer for use with OpenAI models in PostgreSQL. Source: README.md

pg_tiktoken is a PostgreSQL extension that provides input tokenization using OpenAI’s tiktoken library. It allows you to count and encode tokens directly in SQL, which is useful for managing input length limits when working with OpenAI models.

Functions

tiktoken_count

Count the number of tokens for a given encoding or model:

SELECT tiktoken_count('p50k_edit', 'A long time ago in a galaxy far, far away');
 tiktoken_count
----------------
             11
(1 row)

tiktoken_encode

Get the token IDs for a given encoding or model:

SELECT tiktoken_encode('cl100k_base', 'A long time ago in a galaxy far, far away');
                  tiktoken_encode
----------------------------------------------------
 {32,1317,892,4227,304,264,34261,3117,11,3117,3201}
(1 row)

Both tiktoken_count and tiktoken_encode accept either an encoding name or an OpenAI model name as the first argument.

Supported Models

Encoding name	OpenAI models
`cl100k_base`	ChatGPT models, `text-embedding-ada-002`
`p50k_base`	Code models, `text-davinci-002`, `text-davinci-003`
`p50k_edit`	Edit models like `text-davinci-edit-001`, `code-davinci-edit-001`
`r50k_base` (or `gpt2`)	GPT-3 models like `davinci`

pg_tiktoken_c

Mon, 01 Jan 0001 00:00:00 +0000

pg_tiktoken_c : Fast tiktoken BPE tokenizer for PostgreSQL implemented in C

Overview

ID	Extension	Package	Version	Category	License	Language
1880	pg_tiktoken_c	pg_tiktoken_c	`1.1`	RAG	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d--	No	Yes	No	Yes	no	no

Relationships
See Also	pg_tiktoken pg_tokenizer pg_jieba pg_cjk_parser zhparser pg_bigm pgroonga dict_xsyn

Built from upstream main snapshot fa2957b; bundles five vocabularies and includes DESTDIR and correctness patches. Upstream README declares Apache-2.0, but the pinned snapshot omits the referenced LICENSE file.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`1.1`	18 17 16 15 14	`pg_tiktoken_c`	-
RPM	PIGSTY	`1.1`	18 17 16 15 14	`pg_tiktoken_c_$v`	-
DEB	PIGSTY	`1.1`	18 17 16 15 14	`postgresql-$v-pg-tiktoken-c`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
el8.aarch64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
el9.x86_64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
el9.aarch64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
el10.x86_64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
el10.aarch64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
d12.x86_64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
d12.aarch64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
d13.x86_64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
d13.aarch64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
u22.x86_64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
u22.aarch64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
u24.x86_64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
u24.aarch64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
u26.x86_64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1
u26.aarch64	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1	PIGSTY 1.1

PG18

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_c_18`	`1.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_c_18-1.1-1PIGSTY.el8.x86_64.rpm
`pg_tiktoken_c_18`	`1.1`	el8.aarch64	pigsty	2.3 MiB	pg_tiktoken_c_18-1.1-1PIGSTY.el8.aarch64.rpm
`pg_tiktoken_c_18`	`1.1`	el9.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_18-1.1-1PIGSTY.el9.x86_64.rpm
`pg_tiktoken_c_18`	`1.1`	el9.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_18-1.1-1PIGSTY.el9.aarch64.rpm
`pg_tiktoken_c_18`	`1.1`	el10.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_18-1.1-1PIGSTY.el10.x86_64.rpm
`pg_tiktoken_c_18`	`1.1`	el10.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_18-1.1-1PIGSTY.el10.aarch64.rpm
`postgresql-18-pg-tiktoken-c`	`1.1`	d12.x86_64	pigsty	1.8 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~bookworm_amd64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	d12.aarch64	pigsty	1.8 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~bookworm_arm64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	d13.x86_64	pigsty	1.8 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~trixie_amd64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	d13.aarch64	pigsty	1.8 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~trixie_arm64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~jammy_amd64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	u22.aarch64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~jammy_arm64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~noble_amd64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	u24.aarch64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~noble_arm64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~resolute_amd64.deb
`postgresql-18-pg-tiktoken-c`	`1.1`	u26.aarch64	pigsty	2.1 MiB	postgresql-18-pg-tiktoken-c_1.1-1PIGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_c_17`	`1.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_c_17-1.1-1PIGSTY.el8.x86_64.rpm
`pg_tiktoken_c_17`	`1.1`	el8.aarch64	pigsty	2.3 MiB	pg_tiktoken_c_17-1.1-1PIGSTY.el8.aarch64.rpm
`pg_tiktoken_c_17`	`1.1`	el9.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_17-1.1-1PIGSTY.el9.x86_64.rpm
`pg_tiktoken_c_17`	`1.1`	el9.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_17-1.1-1PIGSTY.el9.aarch64.rpm
`pg_tiktoken_c_17`	`1.1`	el10.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_17-1.1-1PIGSTY.el10.x86_64.rpm
`pg_tiktoken_c_17`	`1.1`	el10.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_17-1.1-1PIGSTY.el10.aarch64.rpm
`postgresql-17-pg-tiktoken-c`	`1.1`	d12.x86_64	pigsty	1.8 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~bookworm_amd64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	d12.aarch64	pigsty	1.8 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~bookworm_arm64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	d13.x86_64	pigsty	1.8 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~trixie_amd64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	d13.aarch64	pigsty	1.8 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~trixie_arm64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~jammy_amd64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	u22.aarch64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~jammy_arm64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~noble_amd64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	u24.aarch64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~noble_arm64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~resolute_amd64.deb
`postgresql-17-pg-tiktoken-c`	`1.1`	u26.aarch64	pigsty	2.1 MiB	postgresql-17-pg-tiktoken-c_1.1-1PIGSTY~resolute_arm64.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_c_16`	`1.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_c_16-1.1-1PIGSTY.el8.x86_64.rpm
`pg_tiktoken_c_16`	`1.1`	el8.aarch64	pigsty	2.3 MiB	pg_tiktoken_c_16-1.1-1PIGSTY.el8.aarch64.rpm
`pg_tiktoken_c_16`	`1.1`	el9.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_16-1.1-1PIGSTY.el9.x86_64.rpm
`pg_tiktoken_c_16`	`1.1`	el9.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_16-1.1-1PIGSTY.el9.aarch64.rpm
`pg_tiktoken_c_16`	`1.1`	el10.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_16-1.1-1PIGSTY.el10.x86_64.rpm
`pg_tiktoken_c_16`	`1.1`	el10.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_16-1.1-1PIGSTY.el10.aarch64.rpm
`postgresql-16-pg-tiktoken-c`	`1.1`	d12.x86_64	pigsty	1.8 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~bookworm_amd64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	d12.aarch64	pigsty	1.8 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~bookworm_arm64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	d13.x86_64	pigsty	1.8 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~trixie_amd64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	d13.aarch64	pigsty	1.8 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~trixie_arm64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~jammy_amd64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	u22.aarch64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~jammy_arm64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~noble_amd64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	u24.aarch64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~noble_arm64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~resolute_amd64.deb
`postgresql-16-pg-tiktoken-c`	`1.1`	u26.aarch64	pigsty	2.1 MiB	postgresql-16-pg-tiktoken-c_1.1-1PIGSTY~resolute_arm64.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_c_15`	`1.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_c_15-1.1-1PIGSTY.el8.x86_64.rpm
`pg_tiktoken_c_15`	`1.1`	el8.aarch64	pigsty	2.3 MiB	pg_tiktoken_c_15-1.1-1PIGSTY.el8.aarch64.rpm
`pg_tiktoken_c_15`	`1.1`	el9.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_15-1.1-1PIGSTY.el9.x86_64.rpm
`pg_tiktoken_c_15`	`1.1`	el9.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_15-1.1-1PIGSTY.el9.aarch64.rpm
`pg_tiktoken_c_15`	`1.1`	el10.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_15-1.1-1PIGSTY.el10.x86_64.rpm
`pg_tiktoken_c_15`	`1.1`	el10.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_15-1.1-1PIGSTY.el10.aarch64.rpm
`postgresql-15-pg-tiktoken-c`	`1.1`	d12.x86_64	pigsty	1.8 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~bookworm_amd64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	d12.aarch64	pigsty	1.8 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~bookworm_arm64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	d13.x86_64	pigsty	1.8 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~trixie_amd64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	d13.aarch64	pigsty	1.8 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~trixie_arm64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~jammy_amd64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	u22.aarch64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~jammy_arm64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~noble_amd64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	u24.aarch64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~noble_arm64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~resolute_amd64.deb
`postgresql-15-pg-tiktoken-c`	`1.1`	u26.aarch64	pigsty	2.1 MiB	postgresql-15-pg-tiktoken-c_1.1-1PIGSTY~resolute_arm64.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`pg_tiktoken_c_14`	`1.1`	el8.x86_64	pigsty	2.3 MiB	pg_tiktoken_c_14-1.1-1PIGSTY.el8.x86_64.rpm
`pg_tiktoken_c_14`	`1.1`	el8.aarch64	pigsty	2.3 MiB	pg_tiktoken_c_14-1.1-1PIGSTY.el8.aarch64.rpm
`pg_tiktoken_c_14`	`1.1`	el9.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_14-1.1-1PIGSTY.el9.x86_64.rpm
`pg_tiktoken_c_14`	`1.1`	el9.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_14-1.1-1PIGSTY.el9.aarch64.rpm
`pg_tiktoken_c_14`	`1.1`	el10.x86_64	pigsty	2.0 MiB	pg_tiktoken_c_14-1.1-1PIGSTY.el10.x86_64.rpm
`pg_tiktoken_c_14`	`1.1`	el10.aarch64	pigsty	2.0 MiB	pg_tiktoken_c_14-1.1-1PIGSTY.el10.aarch64.rpm
`postgresql-14-pg-tiktoken-c`	`1.1`	d12.x86_64	pigsty	1.8 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~bookworm_amd64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	d12.aarch64	pigsty	1.8 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~bookworm_arm64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	d13.x86_64	pigsty	1.8 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~trixie_amd64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	d13.aarch64	pigsty	1.8 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~trixie_arm64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	u22.x86_64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~jammy_amd64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	u22.aarch64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~jammy_arm64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	u24.x86_64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~noble_amd64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	u24.aarch64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~noble_arm64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	u26.x86_64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~resolute_amd64.deb
`postgresql-14-pg-tiktoken-c`	`1.1`	u26.aarch64	pigsty	2.1 MiB	postgresql-14-pg-tiktoken-c_1.1-1PIGSTY~resolute_arm64.deb

Source

Repository

github.com/relytcloud/pg_tiktoken_c

Source Tarball

pg_tiktoken_c-1.1.tar.gz

pig build pkg pg_tiktoken_c;		# 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_tiktoken_c;		# install via package name, for the active PG version

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

Create this extension with:

CREATE EXTENSION pg_tiktoken_c;

Usage

Sources:

pg_tiktoken_c implements OpenAI-compatible tiktoken encoding in C inside PostgreSQL. Use it to count or materialize tokens near stored text and to split text into token-bounded chunks before embedding or model requests.

Create the Extension

CREATE EXTENSION pg_tiktoken_c;

The implementation depends on PCRE2 10.30 or later at build time. It does not require shared_preload_libraries; vocabulary data is loaded and cached per backend as encodings are used.

Encode and Count

SELECT tiktoken_encode('cl100k_base', 'PostgreSQL search');
SELECT tiktoken_count('cl100k_base', 'PostgreSQL search');

tiktoken_encode returns a bigint array of token identifiers. tiktoken_count returns the token count without requiring the caller to retain the token array.

The bundled selectors include cl100k_base, o200k_base, r50k_base, p50k_base, and p50k_edit, together with aliases documented by the project. Choose the encoding required by the target model rather than assuming all models share a vocabulary.

Chunk Text

Return chunks as an array:

SELECT chunk_text(
  'long document text',
  chunk_size => 512,
  chunk_overlap => 64,
  encoding => 'cl100k_base'
);

Or return one row per chunk:

SELECT *
FROM chunk_text_table(
  'long document text',
  chunk_size => 512,
  chunk_overlap => 64,
  encoding => 'cl100k_base'
);

chunk_text_table returns chunk_index, chunk, and token_count. The chunk index is zero-based. Overlap repeats boundary tokens between neighboring chunks and must be smaller than the chunk size.

Function Index

tiktoken_encode(selector, text) returns bigint[] token identifiers.
tiktoken_count(selector, text) returns bigint token count.
chunk_text(input_text, chunk_size, chunk_overlap default 0, encoding default cl100k_base) returns text[].
chunk_text_table(input_text, chunk_size, chunk_overlap default 0, encoding default cl100k_base) returns one row per chunk with its index and token count.

The SQL functions are declared immutable and parallel safe. They can therefore be used in generated expressions or parallel plans only when the selected vocabulary files are deployed consistently across every server.

Operational Notes

Tokenization is model-encoding specific. Confirm both the encoding name and the model’s current context limits in the application.
Counting or chunking large text consumes backend CPU and memory; batch large corpora and monitor query latency.
Backend-local caches avoid repeated parsing but increase memory use in sessions that touch several vocabularies.
The upstream README’s compatibility list can lag packaging. Test the exact pg_tiktoken_c build against the target PostgreSQL major version instead of inferring support from a different binary.

pgmnemo

Mon, 01 Jan 0001 00:00:00 +0000

pgmnemo : Single-plan multimodal agent memory for PostgreSQL

Overview

ID	Extension	Package	Version	Category	License	Language
1950	pgmnemo	pgmnemo	`0.16.1`	RAG	Apache-2.0	SQL

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
----dt-	No	No	No	Yes	no	yes

Relationships
Schemas	`pgmnemo`
Requires	vector
See Also	pgcontext vector vectorize pgml pg4ml pg_summarize provsql pg_rrf pg_search

SQL-only extension requiring pgvector 0.7.0 or newer; upstream 0.16.1 and PIGSTY packages support PostgreSQL 17 and 18; the control file lives under extension/.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.16.1`	18 17 16 15 14	`pgmnemo`	`vector`
RPM	PIGSTY	`0.16.1`	18 17 16 15 14	`pgmnemo_$v`	`pgvector_$v`
DEB	PIGSTY	`0.16.1`	18 17 16 15 14	`postgresql-$v-pgmnemo`	`postgresql-$v-pgvector`

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
el8.aarch64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
el9.x86_64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
el9.aarch64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
el10.x86_64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
el10.aarch64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
d12.x86_64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
d12.aarch64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
d13.x86_64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
d13.aarch64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
u22.x86_64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
u22.aarch64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
u24.x86_64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
u24.aarch64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
u26.x86_64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1
u26.aarch64	PIGSTY 0.16.1	PIGSTY 0.16.1	PIGSTY 0.12.1	PIGSTY 0.12.1	PIGSTY 0.12.1

PG18

Package	Version	OS	ORG	SIZE	File URL
`pgmnemo_18`	`0.16.1`	el8.x86_64	pigsty	195.3 KiB	pgmnemo_18-0.16.1-1PIGSTY.el8.noarch.rpm
`pgmnemo_18`	`0.15.0`	el8.x86_64	pigsty	187.2 KiB	pgmnemo_18-0.15.0-1PIGSTY.el8.x86_64.rpm
`pgmnemo_18`	`0.16.1`	el8.aarch64	pigsty	195.3 KiB	pgmnemo_18-0.16.1-1PIGSTY.el8.noarch.rpm
`pgmnemo_18`	`0.15.0`	el8.aarch64	pigsty	187.2 KiB	pgmnemo_18-0.15.0-1PIGSTY.el8.aarch64.rpm
`pgmnemo_18`	`0.16.1`	el9.x86_64	pigsty	176.1 KiB	pgmnemo_18-0.16.1-1PIGSTY.el9.noarch.rpm
`pgmnemo_18`	`0.15.0`	el9.x86_64	pigsty	163.4 KiB	pgmnemo_18-0.15.0-1PIGSTY.el9.x86_64.rpm
`pgmnemo_18`	`0.16.1`	el9.aarch64	pigsty	176.0 KiB	pgmnemo_18-0.16.1-1PIGSTY.el9.noarch.rpm
`pgmnemo_18`	`0.15.0`	el9.aarch64	pigsty	163.3 KiB	pgmnemo_18-0.15.0-1PIGSTY.el9.aarch64.rpm
`pgmnemo_18`	`0.16.1`	el10.x86_64	pigsty	176.3 KiB	pgmnemo_18-0.16.1-1PIGSTY.el10.noarch.rpm
`pgmnemo_18`	`0.15.0`	el10.x86_64	pigsty	163.6 KiB	pgmnemo_18-0.15.0-1PIGSTY.el10.x86_64.rpm
`pgmnemo_18`	`0.16.1`	el10.aarch64	pigsty	176.3 KiB	pgmnemo_18-0.16.1-1PIGSTY.el10.noarch.rpm
`pgmnemo_18`	`0.15.0`	el10.aarch64	pigsty	163.5 KiB	pgmnemo_18-0.15.0-1PIGSTY.el10.aarch64.rpm
`postgresql-18-pgmnemo`	`0.16.1`	d12.x86_64	pigsty	156.8 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~bookworm_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	d12.aarch64	pigsty	156.8 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~bookworm_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	d13.x86_64	pigsty	156.8 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~trixie_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	d13.aarch64	pigsty	156.8 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~trixie_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	u22.x86_64	pigsty	166.2 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~jammy_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	u22.aarch64	pigsty	166.2 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~jammy_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	u24.x86_64	pigsty	165.8 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~noble_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	u24.aarch64	pigsty	165.8 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~noble_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	u26.x86_64	pigsty	165.7 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~resolute_all.deb
`postgresql-18-pgmnemo`	`0.16.1`	u26.aarch64	pigsty	165.7 KiB	postgresql-18-pgmnemo_0.16.1-1PIGSTY~resolute_all.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pgmnemo_17`	`0.16.1`	el8.x86_64	pigsty	195.3 KiB	pgmnemo_17-0.16.1-1PIGSTY.el8.noarch.rpm
`pgmnemo_17`	`0.15.0`	el8.x86_64	pigsty	187.2 KiB	pgmnemo_17-0.15.0-1PIGSTY.el8.x86_64.rpm
`pgmnemo_17`	`0.16.1`	el8.aarch64	pigsty	195.3 KiB	pgmnemo_17-0.16.1-1PIGSTY.el8.noarch.rpm
`pgmnemo_17`	`0.15.0`	el8.aarch64	pigsty	187.2 KiB	pgmnemo_17-0.15.0-1PIGSTY.el8.aarch64.rpm
`pgmnemo_17`	`0.16.1`	el9.x86_64	pigsty	176.0 KiB	pgmnemo_17-0.16.1-1PIGSTY.el9.noarch.rpm
`pgmnemo_17`	`0.15.0`	el9.x86_64	pigsty	163.4 KiB	pgmnemo_17-0.15.0-1PIGSTY.el9.x86_64.rpm
`pgmnemo_17`	`0.16.1`	el9.aarch64	pigsty	176.0 KiB	pgmnemo_17-0.16.1-1PIGSTY.el9.noarch.rpm
`pgmnemo_17`	`0.15.0`	el9.aarch64	pigsty	163.3 KiB	pgmnemo_17-0.15.0-1PIGSTY.el9.aarch64.rpm
`pgmnemo_17`	`0.16.1`	el10.x86_64	pigsty	176.3 KiB	pgmnemo_17-0.16.1-1PIGSTY.el10.noarch.rpm
`pgmnemo_17`	`0.15.0`	el10.x86_64	pigsty	163.6 KiB	pgmnemo_17-0.15.0-1PIGSTY.el10.x86_64.rpm
`pgmnemo_17`	`0.16.1`	el10.aarch64	pigsty	176.3 KiB	pgmnemo_17-0.16.1-1PIGSTY.el10.noarch.rpm
`pgmnemo_17`	`0.15.0`	el10.aarch64	pigsty	163.5 KiB	pgmnemo_17-0.15.0-1PIGSTY.el10.aarch64.rpm
`postgresql-17-pgmnemo`	`0.16.1`	d12.x86_64	pigsty	156.8 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~bookworm_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	d12.aarch64	pigsty	156.8 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~bookworm_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	d13.x86_64	pigsty	156.8 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~trixie_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	d13.aarch64	pigsty	156.8 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~trixie_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	u22.x86_64	pigsty	166.2 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~jammy_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	u22.aarch64	pigsty	166.2 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~jammy_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	u24.x86_64	pigsty	165.8 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~noble_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	u24.aarch64	pigsty	165.8 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~noble_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	u26.x86_64	pigsty	165.6 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~resolute_all.deb
`postgresql-17-pgmnemo`	`0.16.1`	u26.aarch64	pigsty	165.6 KiB	postgresql-17-pgmnemo_0.16.1-1PIGSTY~resolute_all.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`pgmnemo_16`	`0.12.1`	el8.x86_64	pigsty	158.4 KiB	pgmnemo_16-0.12.1-1PIGSTY.el8.x86_64.rpm
`pgmnemo_16`	`0.12.1`	el8.aarch64	pigsty	158.4 KiB	pgmnemo_16-0.12.1-1PIGSTY.el8.aarch64.rpm
`pgmnemo_16`	`0.12.1`	el9.x86_64	pigsty	133.8 KiB	pgmnemo_16-0.12.1-1PIGSTY.el9.x86_64.rpm
`pgmnemo_16`	`0.12.1`	el9.aarch64	pigsty	133.8 KiB	pgmnemo_16-0.12.1-1PIGSTY.el9.aarch64.rpm
`pgmnemo_16`	`0.12.1`	el10.x86_64	pigsty	134.0 KiB	pgmnemo_16-0.12.1-1PIGSTY.el10.x86_64.rpm
`pgmnemo_16`	`0.12.1`	el10.aarch64	pigsty	133.9 KiB	pgmnemo_16-0.12.1-1PIGSTY.el10.aarch64.rpm
`postgresql-16-pgmnemo`	`0.12.1`	d12.x86_64	pigsty	124.2 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~bookworm_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	d12.aarch64	pigsty	124.2 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~bookworm_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	d13.x86_64	pigsty	124.2 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~trixie_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	d13.aarch64	pigsty	124.2 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~trixie_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	u22.x86_64	pigsty	125.1 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~jammy_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	u22.aarch64	pigsty	125.1 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~jammy_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	u24.x86_64	pigsty	124.8 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~noble_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	u24.aarch64	pigsty	124.8 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~noble_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	u26.x86_64	pigsty	124.9 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~resolute_all.deb
`postgresql-16-pgmnemo`	`0.12.1`	u26.aarch64	pigsty	124.9 KiB	postgresql-16-pgmnemo_0.12.1-1PIGSTY~resolute_all.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`pgmnemo_15`	`0.12.1`	el8.x86_64	pigsty	158.4 KiB	pgmnemo_15-0.12.1-1PIGSTY.el8.x86_64.rpm
`pgmnemo_15`	`0.12.1`	el8.aarch64	pigsty	158.4 KiB	pgmnemo_15-0.12.1-1PIGSTY.el8.aarch64.rpm
`pgmnemo_15`	`0.12.1`	el9.x86_64	pigsty	133.8 KiB	pgmnemo_15-0.12.1-1PIGSTY.el9.x86_64.rpm
`pgmnemo_15`	`0.12.1`	el9.aarch64	pigsty	133.8 KiB	pgmnemo_15-0.12.1-1PIGSTY.el9.aarch64.rpm
`pgmnemo_15`	`0.12.1`	el10.x86_64	pigsty	134.0 KiB	pgmnemo_15-0.12.1-1PIGSTY.el10.x86_64.rpm
`pgmnemo_15`	`0.12.1`	el10.aarch64	pigsty	133.9 KiB	pgmnemo_15-0.12.1-1PIGSTY.el10.aarch64.rpm
`postgresql-15-pgmnemo`	`0.12.1`	d12.x86_64	pigsty	124.2 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~bookworm_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	d12.aarch64	pigsty	124.2 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~bookworm_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	d13.x86_64	pigsty	124.2 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~trixie_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	d13.aarch64	pigsty	124.2 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~trixie_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	u22.x86_64	pigsty	125.1 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~jammy_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	u22.aarch64	pigsty	125.1 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~jammy_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	u24.x86_64	pigsty	124.8 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~noble_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	u24.aarch64	pigsty	124.8 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~noble_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	u26.x86_64	pigsty	124.9 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~resolute_all.deb
`postgresql-15-pgmnemo`	`0.12.1`	u26.aarch64	pigsty	124.9 KiB	postgresql-15-pgmnemo_0.12.1-1PIGSTY~resolute_all.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`pgmnemo_14`	`0.12.1`	el8.x86_64	pigsty	158.4 KiB	pgmnemo_14-0.12.1-1PIGSTY.el8.x86_64.rpm
`pgmnemo_14`	`0.12.1`	el8.aarch64	pigsty	158.4 KiB	pgmnemo_14-0.12.1-1PIGSTY.el8.aarch64.rpm
`pgmnemo_14`	`0.12.1`	el9.x86_64	pigsty	133.8 KiB	pgmnemo_14-0.12.1-1PIGSTY.el9.x86_64.rpm
`pgmnemo_14`	`0.12.1`	el9.aarch64	pigsty	133.7 KiB	pgmnemo_14-0.12.1-1PIGSTY.el9.aarch64.rpm
`pgmnemo_14`	`0.12.1`	el10.x86_64	pigsty	134.0 KiB	pgmnemo_14-0.12.1-1PIGSTY.el10.x86_64.rpm
`pgmnemo_14`	`0.12.1`	el10.aarch64	pigsty	133.9 KiB	pgmnemo_14-0.12.1-1PIGSTY.el10.aarch64.rpm
`postgresql-14-pgmnemo`	`0.12.1`	d12.x86_64	pigsty	124.2 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~bookworm_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	d12.aarch64	pigsty	124.2 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~bookworm_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	d13.x86_64	pigsty	124.2 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~trixie_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	d13.aarch64	pigsty	124.2 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~trixie_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	u22.x86_64	pigsty	125.1 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~jammy_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	u22.aarch64	pigsty	125.1 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~jammy_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	u24.x86_64	pigsty	124.8 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~noble_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	u24.aarch64	pigsty	124.8 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~noble_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	u26.x86_64	pigsty	124.9 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~resolute_all.deb
`postgresql-14-pgmnemo`	`0.12.1`	u26.aarch64	pigsty	124.9 KiB	postgresql-14-pgmnemo_0.12.1-1PIGSTY~resolute_all.deb

Source

Repository

github.com/pgmnemo/pgmnemo

Source Tarball

pgmnemo-0.16.1.tar.gz

pig build pkg pgmnemo;		# 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 pgmnemo;		# install via package name, for the active PG version

pig install pgmnemo -v 18;   # install for PG 18
pig install pgmnemo -v 17;   # install for PG 17

Create this extension with:

CREATE EXTENSION pgmnemo CASCADE; -- requires vector

Usage

Sources:

pgmnemo stores agent memory in PostgreSQL and retrieves it through vector, BM25-style text, graph, metadata, temporal, provenance, and outcome-confidence signals. It installs into schema pgmnemo, requires the vector extension, and expects 1024-dimensional embeddings in its current SQL API.

Version 0.16.1 retains the 0.14 corpus-maintenance surface and adds situation fingerprints, verified situation recall, entity-key extraction, and entity-centered recall.

Install

CREATE EXTENSION IF NOT EXISTS vector;
CREATE EXTENSION IF NOT EXISTS pgmnemo CASCADE;

SELECT pgmnemo.version();
SELECT * FROM pgmnemo.stats();

The v0.16.1 control file marks pgmnemo as trusted, installs it in schema pgmnemo, requires vector, and is not relocatable.

Ingest a Lesson

SELECT pgmnemo.ingest(
  p_role        := 'developer',
  p_project_id  := 1,
  p_topic       := 'security',
  p_lesson_text := 'Rotate signing keys after a compromise.',
  p_importance  := 4,
  p_embedding   := NULL,
  p_commit_sha  := 'abc1234',
  p_metadata    := '{"source":"incident-runbook"}'::jsonb
);

When pgmnemo.gate_strict is enforce, commit_sha or artifact_hash provenance is required. warn accepts an unverified write with an audit warning; off disables the gate.

Recall with Confidence Filtering

Hybrid recall combines embedding and text signals:

SELECT lesson_id, topic, score, match_confidence
FROM pgmnemo.recall_hybrid(
  '<1024-dimensional vector literal>'::vector(1024),
  'JWT rotation key compromise',
  10,
  'developer',
  1,
  0.4,
  0.4,
  60,
  'dag-2026-abc',
  ARRAY['note', 'fact'],
  0.40
);

The final p_min_score argument, added in 0.13.0, removes candidates whose match_confidence is below the threshold before LIMIT is applied. NULL preserves pre-0.13 behavior. The release notes suggest 0.40 as a starting point, not a universal value; calibrate it for the embedding model and feedback quality.

The same p_min_score concept is available in recall_fast, recall_lessons, and pooled recall entry points. recall_lessons routes to hybrid recall when both text and embedding are supplied and pgmnemo.disable_hybrid is off.

Record Outcomes

SELECT pgmnemo.reinforce(1001, 'success', true);
SELECT pgmnemo.reinforce(
  ARRAY[1001, 1002]::bigint[],
  'failure',
  false
);

The third p_used argument records whether the recalled memory was actually used. true or NULL increments use_count; false records the outcome without counting a use. Prefer an explicit value so analytics can distinguish ignored advice from used advice.

Under the default posterior mode, match confidence is:

(success_count + alpha)
/ (success_count + failure_count + alpha + beta)

The default Beta prior is alpha 1 and beta 1. Set pgmnemo.confidence_prior_alpha and pgmnemo.confidence_prior_beta between 0.01 and 100 when a different prior is justified.

Important write helpers include remember_fact, remember_event, remember_relation, add_edge, reembed, and recompute_content. remember_fact supersedes the active fact for an entity/property pair; events remain append-oriented; relations also populate the graph surface.

Use navigate_locate or navigate_locate_dispatch to select candidate IDs within a character budget, then navigate_expand_typed to fetch content and neighboring graph edges.

Situation and Entity Recall

The 0.15 line adds deterministic situation fingerprints and a dedicated recall path:

SELECT pgmnemo.extract_sit_fp(
  'security',
  'failure_class=KEY_ROTATION outcome=COMPLETED'
);
SELECT *
FROM pgmnemo.recall_situation(
  pgmnemo.extract_sit_fp(
    'security',
    'failure_class=KEY_ROTATION outcome=COMPLETED'
  ),
  1,
  'developer',
  10
);

Starting with 0.15.1, recall_situation returns verified memories by default. Set pgmnemo.include_unverified = on only when the caller deliberately accepts memories without provenance verification.

The 0.16 line also extracts stable entity keys into metadata.entity_keys during ingestion and exposes entity-centered recall:

SELECT pgmnemo.extract_entity_keys('The run failed with INFRA_FAILURE.');
SELECT * FROM pgmnemo.recall_entity('failure:INFRA_FAILURE', 10);

These extractors are deterministic classifiers, not semantic entity resolution. Normalize application vocabulary and inspect the generated keys before relying on them for tenancy or authorization decisions.

Configuration Index

pgmnemo.confidence_mode: posterior by default; additive retains the legacy calculation.
pgmnemo.confidence_prior_alpha and pgmnemo.confidence_prior_beta: Bayesian prior parameters.
pgmnemo.confidence_boost_weight: contribution of confidence to ranking; defaults to 0, so confidence does not change rank unless enabled.
pgmnemo.gate_strict and pgmnemo.include_unverified: provenance enforcement and retrieval.
pgmnemo.disable_hybrid and pgmnemo.ef_search: recall strategy and HNSW search breadth.
pgmnemo.track_recall_recency: whether recall updates last_recalled_at and recall_count.
pgmnemo.max_query_text_chars, pgmnemo.tenant_id, and pgmnemo.test_project_floor: text, tenancy, and optional test-project controls.

The older confidence-delta settings are deprecated and ignored in posterior mode.

Caveats

Use PostgreSQL 17 or 18 for pgmnemo 0.16.1. The tagged changelog notes that syntax introduced in the 0.10 line makes older PostgreSQL 14-16 compatibility claims inaccurate; current Pigsty packages target 17-18.

Corpus-maintenance operations are read-only by default:

SELECT * FROM pgmnemo.reclassify_corpus();
SELECT * FROM pgmnemo.consolidate(
  p_threshold := 0.92,
  p_dry_run := true,
  p_role := NULL,
  p_limit := 100
);
SELECT * FROM pgmnemo.undo_consolidate(
  p_canonical_id := 42,
  p_dry_run := true
);

Set p_dry_run := false only after reviewing the result inside a transaction. In 0.14.2, reclassification touches only null or classifier-owned types and preserves curator-owned types such as event and relation. Consolidation marks noncanonical lessons superseded, writes edges, and accumulates evidence counts; undo_consolidate uses those edges to restore a selected cluster.

Recall can write recency metadata. Disable pgmnemo.track_recall_recency for read-only analysis.
The confidence model is only as reliable as reinforcement feedback. Avoid treating posterior values as calibrated probabilities without evaluation.
HNSW, text, graph, and metadata indexes increase write and maintenance cost.
The default confidence_boost_weight of 0 means p_min_score can filter results while confidence still contributes nothing to ranking.
Classification is a deterministic keyword and regular-expression heuristic, not semantic review. Always inspect dry-run distributions and proposed duplicate clusters before applying corpus changes.

pgcontext

Mon, 01 Jan 0001 00:00:00 +0000

pgcontext : Vector, filter-aware HNSW, and hybrid retrieval over authoritative PostgreSQL tables.

Overview

ID	Extension	Package	Version	Category	License	Language
1960	pgcontext	pgcontext	`0.2.0`	RAG	Apache-2.0	Rust

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d--	No	Yes	No	Yes	no	no

Relationships
Schemas	`pgcontext`
Need By	pgcontext_pgvector
See Also	vector vectorize vchord vectorscale pg_rrf pg_search pg_bestmatch vchord_bm25 pgmnemo pg_summarize
Siblings	pgcontext_pgvector

Upstream 0.2.0 and PIGSTY packages support PostgreSQL 17 and 18; pgcontext_pgvector ships in the same package.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.2.0`	18 17 16 15 14	`pgcontext`	-
RPM	PIGSTY	`0.2.0`	18 17 16 15 14	`pgcontext_$v`	-
DEB	PIGSTY	`0.2.0`	18 17 16 15 14	`postgresql-$v-pgcontext`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el8.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el9.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el9.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el10.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el10.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
d12.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
d12.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
d13.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
d13.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u22.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u22.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u24.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u24.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u26.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u26.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A

PG18

Package	Version	OS	ORG	SIZE	File URL
`pgcontext_18`	`0.2.0`	el8.x86_64	pigsty	3.9 MiB	pgcontext_18-0.2.0-1PIGSTY.el8.x86_64.rpm
`pgcontext_18`	`0.2.0`	el8.aarch64	pigsty	3.5 MiB	pgcontext_18-0.2.0-1PIGSTY.el8.aarch64.rpm
`pgcontext_18`	`0.2.0`	el9.x86_64	pigsty	3.8 MiB	pgcontext_18-0.2.0-1PIGSTY.el9.x86_64.rpm
`pgcontext_18`	`0.2.0`	el9.aarch64	pigsty	3.6 MiB	pgcontext_18-0.2.0-1PIGSTY.el9.aarch64.rpm
`pgcontext_18`	`0.2.0`	el10.x86_64	pigsty	3.8 MiB	pgcontext_18-0.2.0-1PIGSTY.el10.x86_64.rpm
`pgcontext_18`	`0.2.0`	el10.aarch64	pigsty	3.6 MiB	pgcontext_18-0.2.0-1PIGSTY.el10.aarch64.rpm
`postgresql-18-pgcontext`	`0.2.0`	d12.x86_64	pigsty	3.0 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~bookworm_amd64.deb
`postgresql-18-pgcontext`	`0.2.0`	d12.aarch64	pigsty	2.6 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~bookworm_arm64.deb
`postgresql-18-pgcontext`	`0.2.0`	d13.x86_64	pigsty	3.0 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~trixie_amd64.deb
`postgresql-18-pgcontext`	`0.2.0`	d13.aarch64	pigsty	2.6 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~trixie_arm64.deb
`postgresql-18-pgcontext`	`0.2.0`	u22.x86_64	pigsty	3.4 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~jammy_amd64.deb
`postgresql-18-pgcontext`	`0.2.0`	u22.aarch64	pigsty	3.0 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~jammy_arm64.deb
`postgresql-18-pgcontext`	`0.2.0`	u24.x86_64	pigsty	3.3 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~noble_amd64.deb
`postgresql-18-pgcontext`	`0.2.0`	u24.aarch64	pigsty	3.0 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~noble_arm64.deb
`postgresql-18-pgcontext`	`0.2.0`	u26.x86_64	pigsty	3.3 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~resolute_amd64.deb
`postgresql-18-pgcontext`	`0.2.0`	u26.aarch64	pigsty	3.0 MiB	postgresql-18-pgcontext_0.2.0-1PIGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pgcontext_17`	`0.2.0`	el8.x86_64	pigsty	3.9 MiB	pgcontext_17-0.2.0-1PIGSTY.el8.x86_64.rpm
`pgcontext_17`	`0.2.0`	el8.aarch64	pigsty	3.5 MiB	pgcontext_17-0.2.0-1PIGSTY.el8.aarch64.rpm
`pgcontext_17`	`0.2.0`	el9.x86_64	pigsty	3.8 MiB	pgcontext_17-0.2.0-1PIGSTY.el9.x86_64.rpm
`pgcontext_17`	`0.2.0`	el9.aarch64	pigsty	3.6 MiB	pgcontext_17-0.2.0-1PIGSTY.el9.aarch64.rpm
`pgcontext_17`	`0.2.0`	el10.x86_64	pigsty	3.8 MiB	pgcontext_17-0.2.0-1PIGSTY.el10.x86_64.rpm
`pgcontext_17`	`0.2.0`	el10.aarch64	pigsty	3.6 MiB	pgcontext_17-0.2.0-1PIGSTY.el10.aarch64.rpm
`postgresql-17-pgcontext`	`0.2.0`	d12.x86_64	pigsty	3.0 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~bookworm_amd64.deb
`postgresql-17-pgcontext`	`0.2.0`	d12.aarch64	pigsty	2.6 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~bookworm_arm64.deb
`postgresql-17-pgcontext`	`0.2.0`	d13.x86_64	pigsty	3.0 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~trixie_amd64.deb
`postgresql-17-pgcontext`	`0.2.0`	d13.aarch64	pigsty	2.6 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~trixie_arm64.deb
`postgresql-17-pgcontext`	`0.2.0`	u22.x86_64	pigsty	3.4 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~jammy_amd64.deb
`postgresql-17-pgcontext`	`0.2.0`	u22.aarch64	pigsty	3.0 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~jammy_arm64.deb
`postgresql-17-pgcontext`	`0.2.0`	u24.x86_64	pigsty	3.3 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~noble_amd64.deb
`postgresql-17-pgcontext`	`0.2.0`	u24.aarch64	pigsty	3.0 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~noble_arm64.deb
`postgresql-17-pgcontext`	`0.2.0`	u26.x86_64	pigsty	3.3 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~resolute_amd64.deb
`postgresql-17-pgcontext`	`0.2.0`	u26.aarch64	pigsty	3.0 MiB	postgresql-17-pgcontext_0.2.0-1PIGSTY~resolute_arm64.deb

Source

Repository

pgxn.org/dist/pgContext/0.2.0/

Source Tarball

pgcontext-0.2.0.tar.gz

pig build pkg pgcontext;		# 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 pgcontext;		# install via package name, for the active PG version

pig install pgcontext -v 18;   # install for PG 18
pig install pgcontext -v 17;   # install for PG 17

Create this extension with:

CREATE EXTENSION pgcontext;

Usage

Sources:

pgcontext keeps vector and hybrid retrieval inside PostgreSQL. It provides pgContext-owned vector types, collection metadata over application tables, registered-field filters, exact search, persisted HNSW, and dense plus full-text fusion. Application rows remain authoritative for MVCC, ACL/RLS, backup, and replication; indexes and generated artifacts are rebuildable acceleration state.

Version 0.2.0 targets PostgreSQL 17 and 18, with the release’s controlled-pilot qualification centered on PostgreSQL 17. Advanced HNSW, non-dense, quantized, mapped, and late-interaction paths retain explicit experimental boundaries.

Core Workflow

CREATE EXTENSION pgcontext;

CREATE TABLE public.docs (
    id text PRIMARY KEY,
    embedding pgcontext.vector(2) NOT NULL,
    status text NOT NULL,
    body text NOT NULL,
    metadata jsonb NOT NULL
);

INSERT INTO public.docs (id, embedding, status, body, metadata) VALUES
    ('doc-1', '[1,0]'::pgcontext.vector, 'published', 'postgres vector search', '{"topic":"postgres"}'),
    ('doc-2', '[0,1]'::pgcontext.vector, 'published', 'rust extension guide', '{"topic":"rust"}');

SELECT * FROM pgcontext.create_collection('docs', 'public.docs');
SELECT pgcontext.register_vector('docs', 'embedding', 'embedding', 2, 'l2');
SELECT pgcontext.register_filter_column('docs', 'status', 'status');
SELECT pgcontext.register_jsonb_path('docs', 'topic', 'metadata', ARRAY['topic']);
SELECT pgcontext.upsert_points('docs', ARRAY['doc-1', 'doc-2']);

SELECT source_key, score
FROM pgcontext.search(
    'docs',
    '[1,0]'::pgcontext.vector,
    '{"must":[{"key":"status","match":"published"}]}'::jsonb,
    10
);

Collections describe application-owned tables; they do not copy those rows into another authoritative store. Search, count, facets, grouping, scrolling, recommendation, and discovery share registered vector and filter definitions.

HNSW and Hybrid Retrieval

SET maintenance_work_mem = '2GB';
CREATE INDEX docs_embedding_hnsw ON public.docs
    USING pgcontext_hnsw
    (embedding pgcontext.vector_hnsw_cosine_ops);
RESET maintenance_work_mem;

SELECT source_key, score
FROM pgcontext.query(
    'docs',
    '[1,0]'::pgcontext.vector,
    'postgres search',
    'body',
    10
);

Dense HNSW operator classes cover L2, inner product, cosine, and L1. Index builds enforce maintenance_work_mem; size the build budget first, then compare approximate results with exact search and pgcontext.recall_check. pgcontext.query combines dense and PostgreSQL full-text branches with reciprocal-rank fusion.

Important Objects

pgcontext.vector, pgcontext.halfvec, pgcontext.sparsevec, and pgcontext.bitvec are extension-owned types; the non-dense variants remain experimental.
pgcontext.create_collection, registration functions, and point-mapping functions define the retrieval contract over source tables.
pgcontext.search, count, facet, scroll, grouped_search, recommend, and discover provide table-backed retrieval.
pgcontext.query and explain expose composable and hybrid retrieval.
pgcontext_hnsw plus metric-specific operator classes provide ANN indexing.
Index status, diagnostics, vacuum advice, recall checks, optimization status, and bounded telemetry support operational review.

Upgrade and pgvector Boundary

Version 0.2.0 moves pgContext-owned types into the fixed pgcontext schema. Existing standalone 0.1.0 installations can use the packaged update as a superuser:

ALTER EXTENSION pgcontext UPDATE TO '0.2.0';

Afterward, qualify types such as pgcontext.vector(1536) or deliberately add the schema to search_path. A 0.1.0 database where public vector types are owned by pgvector is rejected before mutation; inventory dependencies, install 0.2.0 and the separate pgcontext_pgvector bridge, recreate registrations and dependents, and rebuild pgContext indexes over the unchanged pgvector columns.

The main extension has no dependency on pgvector. Its types are distinct from public.vector, public.halfvec, and public.sparsevec; do not assume install order aliases one extension’s types to the other.

Operational Boundaries

CREATE EXTENSION and updates require a PostgreSQL superuser because pgContext installs an access method. Granted application APIs do not require superuser.
No shared_preload_libraries, LOAD, or restart is required by the main extension.
The early-release HNSW on-disk format is not stable; plan and validate index rebuilds across releases rather than treating index files as portable data.
Exact reranking, MVCC, ACL, and RLS checks remain correctness boundaries, but they do not replace workload-specific recall, latency, restart, VACUUM, replication, and failure testing.
Remove collection registrations and inspect dependent application objects before dropping the extension; avoid unreviewed CASCADE.

pgcontext_pgvector

Mon, 01 Jan 0001 00:00:00 +0000

pgcontext : Optional pgvector compatibility bridge for pgcontext HNSW indexes.

Overview

ID	Extension	Package	Version	Category	License	Language
1970	pgcontext_pgvector	pgcontext	`0.2.0`	RAG	Apache-2.0	Rust

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d--	No	Yes	No	Yes	no	no

Relationships
Requires	pgcontext vector
See Also	vector vchord vectorscale vectorize pg_rrf pg_search pg_bestmatch vchord_bm25 pgml
Siblings	pgcontext

Optional control shipped by pgcontext 0.2.0; requires pgcontext and vector.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.2.0`	18 17 16 15 14	`pgcontext`	`pgcontext`, `vector`
RPM	PIGSTY	`0.2.0`	18 17 16 15 14	`pgcontext_$v`	-
DEB	PIGSTY	`0.2.0`	18 17 16 15 14	`postgresql-$v-pgcontext`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el8.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el9.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el9.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el10.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
el10.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
d12.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
d12.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
d13.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
d13.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u22.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u22.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u24.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u24.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u26.x86_64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A
u26.aarch64	PIGSTY 0.2.0	PIGSTY 0.2.0	N/A	N/A	N/A

Source

Repository

pgxn.org/dist/pgContext/0.2.0/

Source Tarball

pgcontext-0.2.0.tar.gz

pig build pkg pgcontext;		# 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 pgcontext;		# install via package name, for the active PG version
pig install pgcontext_pgvector;		# install by extension name, for the current active PG version

pig install pgcontext_pgvector -v 18;   # install for PG 18
pig install pgcontext_pgvector -v 17;   # install for PG 17

Create this extension with:

CREATE EXTENSION pgcontext_pgvector CASCADE; -- requires pgcontext, vector

Usage

Sources:

pgcontext_pgvector is the optional pgContext companion bridge for serving pgContext HNSW indexes over columns owned by the pgvector extension. It does not merge the two type systems or copy application data; it adds certified casts, support functions, and operator classes while exact distance semantics remain bound to pgvector operators.

Certified Profile and Installation

Version 0.2.0 fails closed unless the database uses PostgreSQL 17, pgContext 0.2.0, and pgvector 0.8.x installed in public. Install the prerequisites and bridge explicitly:

CREATE EXTENSION vector;
CREATE EXTENSION pgcontext;
CREATE EXTENSION pgcontext_pgvector;

The reverse order of the two prerequisite extensions is also valid, but pgcontext_pgvector must come after both. Installation requires superuser privileges.

Index an Existing pgvector Column

CREATE INDEX items_embedding_pgc
    ON items USING pgcontext_hnsw
       (embedding pgcontext.vector_hnsw_pgvector_cosine_ops);

SELECT id
FROM items
ORDER BY embedding <=> $1::public.vector
LIMIT 10;

Existing pgvector-spelled SQL can use the pgContext access method. ANN candidates are resolved to live heap rows and reranked with the pgvector operator, preserving its double precision distance result semantics.

Important Objects

pgcontext.vector_hnsw_pgvector_l2_ops, pgcontext.vector_hnsw_pgvector_ip_ops, pgcontext.vector_hnsw_pgvector_cosine_ops, and pgcontext.vector_hnsw_pgvector_l1_ops serve existing public.vector columns.
pgcontext.sparsevec_hnsw_pgvector_cosine_ops serves certified public.sparsevec columns, subject to the documented 16,000-dimension and page-envelope limits.
pgcontext.migration_report() inventories pgvector columns, dependencies, HNSW, and IVFFlat without requiring the bridge.
Ownership-conversion functions provide reviewed fast or restricted-online workflows; IVFFlat is rebuilt as HNSW rather than converted in place.

Dependency and Removal Boundaries

The main pgcontext extension remains independent of pgvector. Bridge indexes depend on pgcontext_pgvector, and the bridge depends on both parent extensions, so PostgreSQL blocks removal under RESTRICT until those indexes are removed or converted.

Do not use DROP EXTENSION vector CASCADE as a migration method. Inventory arrays, views, functions, prepared sessions, expression indexes, and other application dependencies first. The bridge does not provide every pgvector helper, IVFFlat, iterative-scan GUC, parallel-build, subvector, or progress-reporting behavior.

No preload or restart is required. The bridge is a privileged compatibility surface, not a promise that all future pgContext, pgvector, PostgreSQL-major, or on-disk index combinations are compatible; rerun the certified preflight and rebuild validation when any component changes.

pg_turbovec

Mon, 01 Jan 0001 00:00:00 +0000

pg_turbovec : TurboQuant-compressed vector type and ANN index access method for PostgreSQL.

Overview

ID	Extension	Package	Version	Category	License	Language
1980	pg_turbovec	pg_turbovec	`1.29.0`	RAG	Apache-2.0	Rust

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d--	No	Yes	No	Yes	no	no

Relationships
Schemas	`turbovec`
See Also	pg_turboquant vector vchord vectorscale

Upstream v1.29.0 supports PostgreSQL 13-18 with PG19 experimental; PIGSTY RPM and DEB ship 1.29.0 for PostgreSQL 14-18, built with pgrx 0.19.1 against OpenBLAS.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`1.29.0`	18 17 16 15 14	`pg_turbovec`	-
RPM	PIGSTY	`1.29.0`	18 17 16 15 14	`pg_turbovec_$v`	`openblas`
DEB	PIGSTY	`1.29.0`	18 17 16 15 14	`postgresql-$v-pg-turbovec`	`libopenblas0`

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
el8.aarch64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
el9.x86_64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
el9.aarch64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
el10.x86_64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
el10.aarch64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
d12.x86_64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
d12.aarch64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
d13.x86_64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
d13.aarch64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
u22.x86_64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
u22.aarch64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
u24.x86_64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
u24.aarch64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
u26.x86_64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0
u26.aarch64	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0	PIGSTY 1.29.0

PG18

Package	Version	OS	ORG	SIZE	File URL
`pg_turbovec_18`	`1.29.0`	el8.x86_64	pigsty	2.1 MiB	pg_turbovec_18-1.29.0-1PIGSTY.el8.x86_64.rpm
`pg_turbovec_18`	`1.29.0`	el8.aarch64	pigsty	2.0 MiB	pg_turbovec_18-1.29.0-1PIGSTY.el8.aarch64.rpm
`pg_turbovec_18`	`1.29.0`	el9.x86_64	pigsty	2.1 MiB	pg_turbovec_18-1.29.0-1PIGSTY.el9.x86_64.rpm
`pg_turbovec_18`	`1.29.0`	el9.aarch64	pigsty	2.1 MiB	pg_turbovec_18-1.29.0-1PIGSTY.el9.aarch64.rpm
`pg_turbovec_18`	`1.29.0`	el10.x86_64	pigsty	2.1 MiB	pg_turbovec_18-1.29.0-1PIGSTY.el10.x86_64.rpm
`pg_turbovec_18`	`1.29.0`	el10.aarch64	pigsty	2.1 MiB	pg_turbovec_18-1.29.0-1PIGSTY.el10.aarch64.rpm
`postgresql-18-pg-turbovec`	`1.29.0`	d12.x86_64	pigsty	1.8 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~bookworm_amd64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	d12.aarch64	pigsty	1.7 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~bookworm_arm64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	d13.x86_64	pigsty	1.8 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~trixie_amd64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	d13.aarch64	pigsty	1.7 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~trixie_arm64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	u22.x86_64	pigsty	2.0 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~jammy_amd64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	u22.aarch64	pigsty	1.9 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~jammy_arm64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	u24.x86_64	pigsty	2.0 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~noble_amd64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	u24.aarch64	pigsty	1.9 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~noble_arm64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	u26.x86_64	pigsty	2.0 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~resolute_amd64.deb
`postgresql-18-pg-turbovec`	`1.29.0`	u26.aarch64	pigsty	1.9 MiB	postgresql-18-pg-turbovec_1.29.0-1PGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pg_turbovec_17`	`1.29.0`	el8.x86_64	pigsty	2.1 MiB	pg_turbovec_17-1.29.0-1PIGSTY.el8.x86_64.rpm
`pg_turbovec_17`	`1.29.0`	el8.aarch64	pigsty	2.0 MiB	pg_turbovec_17-1.29.0-1PIGSTY.el8.aarch64.rpm
`pg_turbovec_17`	`1.29.0`	el9.x86_64	pigsty	2.1 MiB	pg_turbovec_17-1.29.0-1PIGSTY.el9.x86_64.rpm
`pg_turbovec_17`	`1.29.0`	el9.aarch64	pigsty	2.1 MiB	pg_turbovec_17-1.29.0-1PIGSTY.el9.aarch64.rpm
`pg_turbovec_17`	`1.29.0`	el10.x86_64	pigsty	2.1 MiB	pg_turbovec_17-1.29.0-1PIGSTY.el10.x86_64.rpm
`pg_turbovec_17`	`1.29.0`	el10.aarch64	pigsty	2.1 MiB	pg_turbovec_17-1.29.0-1PIGSTY.el10.aarch64.rpm
`postgresql-17-pg-turbovec`	`1.29.0`	d12.x86_64	pigsty	1.8 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~bookworm_amd64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	d12.aarch64	pigsty	1.7 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~bookworm_arm64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	d13.x86_64	pigsty	1.8 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~trixie_amd64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	d13.aarch64	pigsty	1.7 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~trixie_arm64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	u22.x86_64	pigsty	2.0 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~jammy_amd64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	u22.aarch64	pigsty	1.9 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~jammy_arm64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	u24.x86_64	pigsty	2.0 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~noble_amd64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	u24.aarch64	pigsty	1.9 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~noble_arm64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	u26.x86_64	pigsty	2.0 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~resolute_amd64.deb
`postgresql-17-pg-turbovec`	`1.29.0`	u26.aarch64	pigsty	1.9 MiB	postgresql-17-pg-turbovec_1.29.0-1PGSTY~resolute_arm64.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`pg_turbovec_16`	`1.29.0`	el8.x86_64	pigsty	2.1 MiB	pg_turbovec_16-1.29.0-1PIGSTY.el8.x86_64.rpm
`pg_turbovec_16`	`1.29.0`	el8.aarch64	pigsty	2.0 MiB	pg_turbovec_16-1.29.0-1PIGSTY.el8.aarch64.rpm
`pg_turbovec_16`	`1.29.0`	el9.x86_64	pigsty	2.1 MiB	pg_turbovec_16-1.29.0-1PIGSTY.el9.x86_64.rpm
`pg_turbovec_16`	`1.29.0`	el9.aarch64	pigsty	2.1 MiB	pg_turbovec_16-1.29.0-1PIGSTY.el9.aarch64.rpm
`pg_turbovec_16`	`1.29.0`	el10.x86_64	pigsty	2.1 MiB	pg_turbovec_16-1.29.0-1PIGSTY.el10.x86_64.rpm
`pg_turbovec_16`	`1.29.0`	el10.aarch64	pigsty	2.1 MiB	pg_turbovec_16-1.29.0-1PIGSTY.el10.aarch64.rpm
`postgresql-16-pg-turbovec`	`1.29.0`	d12.x86_64	pigsty	1.8 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~bookworm_amd64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	d12.aarch64	pigsty	1.7 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~bookworm_arm64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	d13.x86_64	pigsty	1.8 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~trixie_amd64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	d13.aarch64	pigsty	1.7 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~trixie_arm64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	u22.x86_64	pigsty	2.0 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~jammy_amd64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	u22.aarch64	pigsty	1.9 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~jammy_arm64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	u24.x86_64	pigsty	2.0 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~noble_amd64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	u24.aarch64	pigsty	1.9 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~noble_arm64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	u26.x86_64	pigsty	1.9 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~resolute_amd64.deb
`postgresql-16-pg-turbovec`	`1.29.0`	u26.aarch64	pigsty	1.9 MiB	postgresql-16-pg-turbovec_1.29.0-1PGSTY~resolute_arm64.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`pg_turbovec_15`	`1.29.0`	el8.x86_64	pigsty	2.1 MiB	pg_turbovec_15-1.29.0-1PIGSTY.el8.x86_64.rpm
`pg_turbovec_15`	`1.29.0`	el8.aarch64	pigsty	2.0 MiB	pg_turbovec_15-1.29.0-1PIGSTY.el8.aarch64.rpm
`pg_turbovec_15`	`1.29.0`	el9.x86_64	pigsty	2.1 MiB	pg_turbovec_15-1.29.0-1PIGSTY.el9.x86_64.rpm
`pg_turbovec_15`	`1.29.0`	el9.aarch64	pigsty	2.1 MiB	pg_turbovec_15-1.29.0-1PIGSTY.el9.aarch64.rpm
`pg_turbovec_15`	`1.29.0`	el10.x86_64	pigsty	2.1 MiB	pg_turbovec_15-1.29.0-1PIGSTY.el10.x86_64.rpm
`pg_turbovec_15`	`1.29.0`	el10.aarch64	pigsty	2.1 MiB	pg_turbovec_15-1.29.0-1PIGSTY.el10.aarch64.rpm
`postgresql-15-pg-turbovec`	`1.29.0`	d12.x86_64	pigsty	1.8 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~bookworm_amd64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	d12.aarch64	pigsty	1.6 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~bookworm_arm64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	d13.x86_64	pigsty	1.8 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~trixie_amd64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	d13.aarch64	pigsty	1.6 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~trixie_arm64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	u22.x86_64	pigsty	2.0 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~jammy_amd64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	u22.aarch64	pigsty	1.9 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~jammy_arm64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	u24.x86_64	pigsty	2.0 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~noble_amd64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	u24.aarch64	pigsty	1.9 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~noble_arm64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	u26.x86_64	pigsty	1.9 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~resolute_amd64.deb
`postgresql-15-pg-turbovec`	`1.29.0`	u26.aarch64	pigsty	1.9 MiB	postgresql-15-pg-turbovec_1.29.0-1PGSTY~resolute_arm64.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`pg_turbovec_14`	`1.29.0`	el8.x86_64	pigsty	2.1 MiB	pg_turbovec_14-1.29.0-1PIGSTY.el8.x86_64.rpm
`pg_turbovec_14`	`1.29.0`	el8.aarch64	pigsty	2.0 MiB	pg_turbovec_14-1.29.0-1PIGSTY.el8.aarch64.rpm
`pg_turbovec_14`	`1.29.0`	el9.x86_64	pigsty	2.1 MiB	pg_turbovec_14-1.29.0-1PIGSTY.el9.x86_64.rpm
`pg_turbovec_14`	`1.29.0`	el9.aarch64	pigsty	2.1 MiB	pg_turbovec_14-1.29.0-1PIGSTY.el9.aarch64.rpm
`pg_turbovec_14`	`1.29.0`	el10.x86_64	pigsty	2.1 MiB	pg_turbovec_14-1.29.0-1PIGSTY.el10.x86_64.rpm
`pg_turbovec_14`	`1.29.0`	el10.aarch64	pigsty	2.1 MiB	pg_turbovec_14-1.29.0-1PIGSTY.el10.aarch64.rpm
`postgresql-14-pg-turbovec`	`1.29.0`	d12.x86_64	pigsty	1.8 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~bookworm_amd64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	d12.aarch64	pigsty	1.6 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~bookworm_arm64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	d13.x86_64	pigsty	1.8 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~trixie_amd64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	d13.aarch64	pigsty	1.6 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~trixie_arm64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	u22.x86_64	pigsty	2.0 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~jammy_amd64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	u22.aarch64	pigsty	1.9 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~jammy_arm64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	u24.x86_64	pigsty	1.9 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~noble_amd64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	u24.aarch64	pigsty	1.9 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~noble_arm64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	u26.x86_64	pigsty	1.9 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~resolute_amd64.deb
`postgresql-14-pg-turbovec`	`1.29.0`	u26.aarch64	pigsty	1.9 MiB	postgresql-14-pg-turbovec_1.29.0-1PGSTY~resolute_arm64.deb

Source

Repository

codeberg.org/gregburd/pg_turbovec

Source Tarball

pg_turbovec-1.29.0.tar.gz

pig build pkg pg_turbovec;		# 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_turbovec;		# install via package name, for the active PG version

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

Create this extension with:

CREATE EXTENSION pg_turbovec;

Usage

Sources:

pg_turbovec 1.29.0 provides a dense turbovec.vector type and a turbovec nearest-neighbor index access method. It quantizes floating-point coordinates to 2, 3, or 4 bits and reranks candidates against heap vectors. Use it for storage-constrained cosine or inner-product search; choose the index kind deliberately because the default flat scan is linear in row count.

Create and Query Vectors

CREATE EXTENSION pg_turbovec;
SET search_path = public, turbovec;

CREATE TABLE items (
  id bigint GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
  embedding turbovec.vector
);

INSERT INTO items (embedding)
VALUES ('[1,2,3]'), ('[4,5,6]');

SELECT id, embedding <=> '[3,1,2]'::turbovec.vector AS cosine_distance
FROM items
ORDER BY embedding <=> '[3,1,2]'::turbovec.vector
LIMIT 10;

Distance operators are <-> for L2, <#> for negative inner product, <=> for cosine distance, and <+> for L1. The current index supports inner-product and cosine ordering; L2 and L1 are exact-only operations.

The turbovec.vector type accepts 1–16,000 coordinates. Indexed vectors must have a fixed dimension that is a multiple of 8; use a check constraint or application validation when the column itself is variable-dimensional.

Choose and Build an Index Kind

-- Default flat quantized scan
CREATE INDEX items_embedding_flat_idx ON items
USING turbovec (embedding vec_cosine_ops)
WITH (bit_width = 4);

-- Out-of-core IVF alternative
CREATE INDEX items_embedding_ivf_idx ON items
USING turbovec (embedding vec_cosine_ops)
WITH (bit_width = 4, lists = 1024);

-- Navigable-graph alternative
CREATE INDEX items_embedding_graph_idx ON items
USING turbovec (embedding vec_cosine_ops)
WITH (bit_width = 4, graph = true);

SET turbovec.probes = 32;

SELECT id
FROM items
ORDER BY embedding <=> '[3,1,2]'::turbovec.vector
LIMIT 10;

These CREATE INDEX statements are alternatives, not a recommendation to keep all three. The default flat kind performs an O(n * dim) quantized scan and can reach exact recall after heap reranking, but it is a poor latency choice at large row counts. WITH (lists = N) enables an out-of-core IVF layer; WITH (graph = true) enables the Vamana graph for lower-latency ANN at moderate scale.

Use vec_cosine_ops with <=> or vec_ip_ops with <#>. bit_width = 4 is the default and generally favors recall; 2-bit indexes are smaller but need workload-specific recall testing. Three-bit indexes are also supported. CREATE INDEX CONCURRENTLY is supported.

Important tuning controls include turbovec.probes, turbovec.search_k, turbovec.oversample, turbovec.hi_dim_rerank, turbovec.iterative_scan, and turbovec.cache_size_mb. Change one dimension at a time and compare approximate results with an exact baseline.

Filtering and Partitioning

Use PostgreSQL partial indexes for stable filter values, the documented turbovec.knn(..., allowed) surface for an explicit candidate allowlist, or iterative scan for normal filtered ORDER BY ... LIMIT queries.

Version 1.29 documents native PostgreSQL partitioning for larger-than-single-table datasets. A parent query can use Merge Append across per-partition TurboVec indexes:

SELECT id
FROM partitioned_items
ORDER BY embedding <=> $1::turbovec.vector
LIMIT 20;

Build, vacuum, and reindex each partition independently. Partition pruning based on a coarse vector quantizer is only a design in 1.29.0, not a shipped feature.

Version and Integrity Boundaries

The control file installs objects in schema turbovec, is not relocatable, and does not require shared_preload_libraries or a server restart.
Upstream v1.29 targets PostgreSQL 13-18 and labels PostgreSQL 19 support experimental; current Pigsty 1.29.0 packages cover PostgreSQL 14-18 and provide the matching OpenBLAS-linked binary.
Upstream 1.28.4 fixes persisted row-count drift that could corrupt the index ID table and adds turbovec.turbovec_check(regclass). An already corrupt index still needs REINDEX or drop/recreate recovery.
Version 1.29.0 is additive, keeps wire format 7, and does not require reindexing when upgrading from a healthy 1.28.4 index. ALTER EXTENSION pg_turbovec UPDATE TO '1.29.0' is sufficient after the new files are installed.
Although the 1.29 reloption parser accepts bit_width = 1, end-to-end one-bit indexing is not implemented and CREATE INDEX intentionally errors. Use bit_width = 2, bit_width = 3, or bit_width = 4.
The on-disk ID table still has a documented crash-safety gap after an unclean shutdown. Treat integrity errors as actionable and follow the upstream recovery guidance.

SELECT *
FROM turbovec.turbovec_check('items_embedding_flat_idx'::regclass);

REINDEX INDEX CONCURRENTLY items_embedding_flat_idx;

Only the index owner can run the integrity checker. Alert on is_corrupt and rebuild the affected index when the checker or a scan reports corruption; a successful version upgrade does not repair an already damaged index.

pg_bestmatch

Mon, 01 Jan 0001 00:00:00 +0000

pg_bestmatch : Generate BM25 sparse vector inside PostgreSQL

Overview

ID	Extension	Package	Version	Category	License	Language
2140	pg_bestmatch	pg_bestmatch	`0.0.2`	FTS	Apache-2.0	Rust

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	No	Yes	Yes	Yes	no	no

Relationships
Schemas	`bm_catalog`
See Also	pg_search pg_textsearch vchord_bm25 pg_fts pg_rrf pgroonga psql_bm25s vectorize pgcontext

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.0.2`	18 17 16 15 14	`pg_bestmatch`	-
RPM	PIGSTY	`0.0.2`	18 17 16 15 14	`pg_bestmatch_$v`	-
DEB	PIGSTY	`0.0.2`	18 17 16 15 14	`postgresql-$v-pg-bestmatch`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
el8.aarch64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
el9.x86_64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
el9.aarch64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
el10.x86_64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
el10.aarch64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
d12.x86_64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
d12.aarch64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
d13.x86_64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
d13.aarch64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
u22.x86_64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
u22.aarch64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
u24.x86_64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
u24.aarch64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
u26.x86_64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2
u26.aarch64	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2	PIGSTY 0.0.2

PG18

Package	Version	OS	ORG	SIZE	File URL
`pg_bestmatch_18`	`0.0.2`	el8.x86_64	pigsty	9.0 MiB	pg_bestmatch_18-0.0.2-3PIGSTY.el8.x86_64.rpm
`pg_bestmatch_18`	`0.0.2`	el8.aarch64	pigsty	8.8 MiB	pg_bestmatch_18-0.0.2-3PIGSTY.el8.aarch64.rpm
`pg_bestmatch_18`	`0.0.2`	el9.x86_64	pigsty	8.7 MiB	pg_bestmatch_18-0.0.2-3PIGSTY.el9.x86_64.rpm
`pg_bestmatch_18`	`0.0.2`	el9.aarch64	pigsty	8.7 MiB	pg_bestmatch_18-0.0.2-3PIGSTY.el9.aarch64.rpm
`pg_bestmatch_18`	`0.0.2`	el10.x86_64	pigsty	8.5 MiB	pg_bestmatch_18-0.0.2-3PIGSTY.el10.x86_64.rpm
`pg_bestmatch_18`	`0.0.2`	el10.aarch64	pigsty	8.5 MiB	pg_bestmatch_18-0.0.2-3PIGSTY.el10.aarch64.rpm
`postgresql-18-pg-bestmatch`	`0.0.2`	d12.x86_64	pigsty	7.4 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~bookworm_amd64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	d12.aarch64	pigsty	7.0 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~bookworm_arm64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	d13.x86_64	pigsty	7.4 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~trixie_amd64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	d13.aarch64	pigsty	7.0 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~trixie_arm64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	u22.x86_64	pigsty	8.1 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~jammy_amd64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	u22.aarch64	pigsty	8.0 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~jammy_arm64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	u24.x86_64	pigsty	8.1 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~noble_amd64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	u24.aarch64	pigsty	8.0 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~noble_arm64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	u26.x86_64	pigsty	8.1 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~resolute_amd64.deb
`postgresql-18-pg-bestmatch`	`0.0.2`	u26.aarch64	pigsty	8.0 MiB	postgresql-18-pg-bestmatch_0.0.2-4PIGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pg_bestmatch_17`	`0.0.2`	el8.x86_64	pigsty	9.0 MiB	pg_bestmatch_17-0.0.2-3PIGSTY.el8.x86_64.rpm
`pg_bestmatch_17`	`0.0.2`	el8.aarch64	pigsty	8.8 MiB	pg_bestmatch_17-0.0.2-3PIGSTY.el8.aarch64.rpm
`pg_bestmatch_17`	`0.0.2`	el9.x86_64	pigsty	8.6 MiB	pg_bestmatch_17-0.0.2-3PIGSTY.el9.x86_64.rpm
`pg_bestmatch_17`	`0.0.2`	el9.aarch64	pigsty	8.7 MiB	pg_bestmatch_17-0.0.2-3PIGSTY.el9.aarch64.rpm
`pg_bestmatch_17`	`0.0.2`	el10.x86_64	pigsty	8.5 MiB	pg_bestmatch_17-0.0.2-3PIGSTY.el10.x86_64.rpm
`pg_bestmatch_17`	`0.0.2`	el10.aarch64	pigsty	8.6 MiB	pg_bestmatch_17-0.0.2-3PIGSTY.el10.aarch64.rpm
`postgresql-17-pg-bestmatch`	`0.0.2`	d12.x86_64	pigsty	7.4 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~bookworm_amd64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	d12.aarch64	pigsty	7.0 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~bookworm_arm64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	d13.x86_64	pigsty	7.4 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~trixie_amd64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	d13.aarch64	pigsty	7.0 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~trixie_arm64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	u22.x86_64	pigsty	8.1 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~jammy_amd64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	u22.aarch64	pigsty	8.0 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~jammy_arm64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	u24.x86_64	pigsty	8.1 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~noble_amd64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	u24.aarch64	pigsty	8.0 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~noble_arm64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	u26.x86_64	pigsty	8.1 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~resolute_amd64.deb
`postgresql-17-pg-bestmatch`	`0.0.2`	u26.aarch64	pigsty	8.0 MiB	postgresql-17-pg-bestmatch_0.0.2-4PIGSTY~resolute_arm64.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`pg_bestmatch_16`	`0.0.2`	el8.x86_64	pigsty	9.0 MiB	pg_bestmatch_16-0.0.2-3PIGSTY.el8.x86_64.rpm
`pg_bestmatch_16`	`0.0.2`	el8.aarch64	pigsty	8.8 MiB	pg_bestmatch_16-0.0.2-3PIGSTY.el8.aarch64.rpm
`pg_bestmatch_16`	`0.0.2`	el9.x86_64	pigsty	8.6 MiB	pg_bestmatch_16-0.0.2-3PIGSTY.el9.x86_64.rpm
`pg_bestmatch_16`	`0.0.2`	el9.aarch64	pigsty	8.7 MiB	pg_bestmatch_16-0.0.2-3PIGSTY.el9.aarch64.rpm
`pg_bestmatch_16`	`0.0.2`	el10.x86_64	pigsty	8.5 MiB	pg_bestmatch_16-0.0.2-3PIGSTY.el10.x86_64.rpm
`pg_bestmatch_16`	`0.0.2`	el10.aarch64	pigsty	8.6 MiB	pg_bestmatch_16-0.0.2-3PIGSTY.el10.aarch64.rpm
`postgresql-16-pg-bestmatch`	`0.0.2`	d12.x86_64	pigsty	7.4 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~bookworm_amd64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	d12.aarch64	pigsty	7.0 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~bookworm_arm64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	d13.x86_64	pigsty	7.4 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~trixie_amd64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	d13.aarch64	pigsty	7.0 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~trixie_arm64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	u22.x86_64	pigsty	8.1 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~jammy_amd64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	u22.aarch64	pigsty	8.0 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~jammy_arm64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	u24.x86_64	pigsty	8.1 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~noble_amd64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	u24.aarch64	pigsty	8.0 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~noble_arm64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	u26.x86_64	pigsty	8.1 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~resolute_amd64.deb
`postgresql-16-pg-bestmatch`	`0.0.2`	u26.aarch64	pigsty	8.0 MiB	postgresql-16-pg-bestmatch_0.0.2-4PIGSTY~resolute_arm64.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`pg_bestmatch_15`	`0.0.2`	el8.x86_64	pigsty	8.9 MiB	pg_bestmatch_15-0.0.2-3PIGSTY.el8.x86_64.rpm
`pg_bestmatch_15`	`0.0.2`	el8.aarch64	pigsty	8.8 MiB	pg_bestmatch_15-0.0.2-3PIGSTY.el8.aarch64.rpm
`pg_bestmatch_15`	`0.0.2`	el9.x86_64	pigsty	8.6 MiB	pg_bestmatch_15-0.0.2-3PIGSTY.el9.x86_64.rpm
`pg_bestmatch_15`	`0.0.2`	el9.aarch64	pigsty	8.7 MiB	pg_bestmatch_15-0.0.2-3PIGSTY.el9.aarch64.rpm
`pg_bestmatch_15`	`0.0.2`	el10.x86_64	pigsty	8.5 MiB	pg_bestmatch_15-0.0.2-3PIGSTY.el10.x86_64.rpm
`pg_bestmatch_15`	`0.0.2`	el10.aarch64	pigsty	8.5 MiB	pg_bestmatch_15-0.0.2-3PIGSTY.el10.aarch64.rpm
`postgresql-15-pg-bestmatch`	`0.0.2`	d12.x86_64	pigsty	7.4 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~bookworm_amd64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	d12.aarch64	pigsty	7.0 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~bookworm_arm64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	d13.x86_64	pigsty	7.4 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~trixie_amd64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	d13.aarch64	pigsty	7.0 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~trixie_arm64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	u22.x86_64	pigsty	8.1 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~jammy_amd64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	u22.aarch64	pigsty	8.0 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~jammy_arm64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	u24.x86_64	pigsty	8.1 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~noble_amd64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	u24.aarch64	pigsty	7.9 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~noble_arm64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	u26.x86_64	pigsty	8.1 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~resolute_amd64.deb
`postgresql-15-pg-bestmatch`	`0.0.2`	u26.aarch64	pigsty	8.0 MiB	postgresql-15-pg-bestmatch_0.0.2-4PIGSTY~resolute_arm64.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`pg_bestmatch_14`	`0.0.2`	el8.x86_64	pigsty	8.9 MiB	pg_bestmatch_14-0.0.2-3PIGSTY.el8.x86_64.rpm
`pg_bestmatch_14`	`0.0.2`	el8.aarch64	pigsty	8.8 MiB	pg_bestmatch_14-0.0.2-3PIGSTY.el8.aarch64.rpm
`pg_bestmatch_14`	`0.0.2`	el9.x86_64	pigsty	8.6 MiB	pg_bestmatch_14-0.0.2-3PIGSTY.el9.x86_64.rpm
`pg_bestmatch_14`	`0.0.2`	el9.aarch64	pigsty	8.7 MiB	pg_bestmatch_14-0.0.2-3PIGSTY.el9.aarch64.rpm
`pg_bestmatch_14`	`0.0.2`	el10.x86_64	pigsty	8.5 MiB	pg_bestmatch_14-0.0.2-3PIGSTY.el10.x86_64.rpm
`pg_bestmatch_14`	`0.0.2`	el10.aarch64	pigsty	8.5 MiB	pg_bestmatch_14-0.0.2-3PIGSTY.el10.aarch64.rpm
`postgresql-14-pg-bestmatch`	`0.0.2`	d12.x86_64	pigsty	7.4 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~bookworm_amd64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	d12.aarch64	pigsty	7.0 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~bookworm_arm64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	d13.x86_64	pigsty	7.4 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~trixie_amd64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	d13.aarch64	pigsty	7.0 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~trixie_arm64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	u22.x86_64	pigsty	8.1 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~jammy_amd64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	u22.aarch64	pigsty	8.0 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~jammy_arm64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	u24.x86_64	pigsty	8.1 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~noble_amd64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	u24.aarch64	pigsty	8.0 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~noble_arm64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	u26.x86_64	pigsty	8.1 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~resolute_amd64.deb
`postgresql-14-pg-bestmatch`	`0.0.2`	u26.aarch64	pigsty	8.0 MiB	postgresql-14-pg-bestmatch_0.0.2-4PIGSTY~resolute_arm64.deb

Source

Repository

github.com/tensorchord/pg_bestmatch.rs

Source Tarball

pg_bestmatch-0.0.2.tar.gz

pig build pkg pg_bestmatch;		# 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_bestmatch;		# install via package name, for the active PG version

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

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_bestmatch';

Create this extension with:

CREATE EXTENSION pg_bestmatch;

Usage

How does it work?

Create an BM25 statistics based on your document set by bm25_create(table_name, column_name, statistic_name);. It will create a materilized view to record the stats.
Generate document sparse vector by bm25_document_to_svector(statistic_name, passage)
For query, generate query sparse vector bm25_query_to_svector(statistic_name, query)
Calculate the score by dot product between the query sparse vector and the document sparse vector
Currently we use huggingface tokenizer with bert-base-uncased vocabulary set to tokenize words. Might support more configuration on tokenizer in the future.

Install

CREATE EXTENSION pg_bestmatch;
SET search_path TO public, bm_catalog;

Example

Here is an example workflow demonstrating the usage of this extension with the example of Stanford LoCo benchmark.

Load the dataset. Here is a script for you if you want to experience pg_bestmatch with the dataset.

wget https://huggingface.co/api/datasets/hazyresearch/LoCoV1-Documents/parquet/default/test/0.parquet -O documents.parquet
wget https://huggingface.co/api/datasets/hazyresearch/LoCoV1-Queries/parquet/default/test/0.parquet -O queries.parquet

import pandas as pd
from sqlalchemy import create_engine
import numpy as np
from psycopg2.extensions import register_adapter, AsIs

def adapter_numpy_float64(numpy_float64):
    return AsIs(numpy_float64)

def adapter_numpy_int64(numpy_int64):
    return AsIs(numpy_int64)

def adapter_numpy_float32(numpy_float32):
    return AsIs(numpy_float32)

def adapter_numpy_int32(numpy_int32):
    return AsIs(numpy_int32)

def adapter_numpy_array(numpy_array):
    return AsIs(tuple(numpy_array))

register_adapter(np.float64, adapter_numpy_float64)
register_adapter(np.int64, adapter_numpy_int64)
register_adapter(np.float32, adapter_numpy_float32)
register_adapter(np.int32, adapter_numpy_int32)
register_adapter(np.ndarray, adapter_numpy_array)

db_url = "postgresql://localhost:5432/pg_bestmatch_test"
engine = create_engine(db_url)

def load_documents():
    df = pd.read_parquet("documents.parquet")
    df.to_sql("documents", engine, if_exists='replace', index=False)

def load_queries():
    df = pd.read_parquet("queries.parquet")
    df['answer_pids'] = df['answer_pids'].apply(lambda x: str(x[0]))    
    df.to_sql("queries", engine, if_exists='replace', index=False)

load_documents()
load_queries()

Create BM25 statistics for the documents table.

SELECT bm25_create('documents', 'passage', 'documents_passage_bm25', 0.75, 1.2);

Add an embedding column to the documents and queries tables and update the embeddings for documents and queries.

ALTER TABLE documents ADD COLUMN embedding svector; -- for pgvecto.rs users
ALTER TABLE documents ADD COLUMN embedding sparsevec; -- for pgvector users

UPDATE documents SET embedding = bm25_document_to_svector('documents_passage_bm25', passage)::svector; -- for pgvecto.rs users
UPDATE documents SET embedding = bm25_document_to_svector('documents_passage_bm25', passage, 'pgvector')::sparsevec; -- for pgvector users

(Optional) Create a vector index on the sparse vector column.

CREATE INDEX ON documents USING vectors (embedding svector_dot_ops); -- for pgvecto.rs users
CREATE INDEX ON documents USING ivfflat (embedding sparsevec_ip_ops); -- for pgvector users

Perform a vector search to find the most relevant documents for each query.

ALTER TABLE queries ADD COLUMN embedding svector; -- for pgvecto.rs users
ALTER TABLE queries ADD COLUMN embedding sparsevec; -- for pgvector users

UPDATE queries SET embedding = bm25_query_to_svector('documents_passage_bm25', query)::svector; -- for pgvecto.rs users
UPDATE queries SET embedding = bm25_query_to_svector('documents_passage_bm25', query, 'pgvector')::sparsevec; -- for pgvector users

SELECT sum((array[answer_pids] = array(SELECT pid FROM documents WHERE queries.dataset = documents.dataset ORDER BY queries.embedding <#> documents.embedding LIMIT 1))::int) FROM queries;

This workflow showcases how to leverage BM25 text queries and vector search in PostgreSQL using this extension. The Top 1 recall of BM25 on this dataset is 0.77. If you reproduce the result, your operations are correct.

Comparison with pg_search

pg_bestmatch.rs only provides methods for generating sparse vectors and does not support index-based search (which can be achieved by pgvecto.rs or pgvector).
pg_search performs BM25 retrieval via the external tantivy engine, which may have limitations when combined with transactions, filters, or JOIN operations. Since pg_bestmatch.rs is entirely native to Postgres, it offers full compatibility with these operations inside postgres.

Reference

tokenize
- Description: Tokenizes an input string into individual tokens.
- Example:
  SELECT tokenize('i have an apple'); -- result: {i,have,an,apple}
bm25_create
- Description: Creates BM25 statistics for a specified table and column.
- Usage:
  SELECT bm25_create('documents', 'passage', 'documents_passage_bm25');
- Parameters:
  - table_name: Name of the table.
  - column_name: Name of the column.
  - stat_name: Name of the BM25 statistics.
  - b: BM25 parameter (default 0.75).
  - k: BM25 parameter (default 1.2).
bm25_refresh
- Description: Updates the BM25 statistics to reflect any changes in the underlying data.
- Usage:
  SELECT bm25_refresh('documents_passage_bm25');
- Parameters:
  - stat_name: Name of the BM25 statistics to update.
bm25_drop
- Description: Deletes the BM25 statistics for a specified table and column.
- Usage:
  SELECT bm25_drop('documents_passage_bm25');
- Parameters:
  - stat_name: Name of the BM25 statistics to delete.
bm25_document_to_svector
- Description: Converts document text into a sparse vector representation.
- Usage:
  SELECT bm25_document_to_svector('documents_passage_bm25', 'document_text');
- Parameters:
  - stat_name: Name of the BM25 statistics.
  - document_text: The text of the document.
  - style: Emits pgvecto.rs-style sparse vector or pgvector-style sparse vector.
bm25_query_to_svector
- Description: Converts query text into a sparse vector representation.
- Usage:
  SELECT bm25_query_to_svector('documents_passage_bm25', 'We begin, as always, with the text.');
- Parameters:
  - stat_name: Name of the BM25 statistics.
  - query_text: The text of the query.
  - style: Emits pgvecto.rs-style sparse vector or pgvector-style sparse vector.

pg_tokenizer

Mon, 01 Jan 0001 00:00:00 +0000

pg_tokenizer : Tokenizers for full-text search

Overview

ID	Extension	Package	Version	Category	License	Language
2160	pg_tokenizer	pg_tokenizer	`0.1.1`	FTS	Apache-2.0	Rust

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	No	Yes	Yes	Yes	no	no

Relationships
Schemas	`tokenizer_catalog`
See Also	pgroonga pg_jieba pg_cjk_parser zhparser pg_bigm pg_tiktoken pg_tiktoken_c unaccent dict_xsyn dict_int hunspell_cs_cz pg_kazsearch

PG18 fix by Vonng.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.1.1`	18 17 16 15 14	`pg_tokenizer`	-
RPM	PIGSTY	`0.1.1`	18 17 16 15 14	`pg_tokenizer_$v`	-
DEB	PIGSTY	`0.1.1`	18 17 16 15 14	`postgresql-$v-pg-tokenizer`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
el8.aarch64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
el9.x86_64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
el9.aarch64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
el10.x86_64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
el10.aarch64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
d12.x86_64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
d12.aarch64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
d13.x86_64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
d13.aarch64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
u22.x86_64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
u22.aarch64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
u24.x86_64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
u24.aarch64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
u26.x86_64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1
u26.aarch64	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1	PIGSTY 0.1.1

PG18

Package	Version	OS	ORG	SIZE	File URL
`pg_tokenizer_18`	`0.1.1`	el8.x86_64	pigsty	13.3 MiB	pg_tokenizer_18-0.1.1-3PIGSTY.el8.x86_64.rpm
`pg_tokenizer_18`	`0.1.1`	el8.aarch64	pigsty	13.0 MiB	pg_tokenizer_18-0.1.1-3PIGSTY.el8.aarch64.rpm
`pg_tokenizer_18`	`0.1.1`	el9.x86_64	pigsty	12.5 MiB	pg_tokenizer_18-0.1.1-3PIGSTY.el9.x86_64.rpm
`pg_tokenizer_18`	`0.1.1`	el9.aarch64	pigsty	12.4 MiB	pg_tokenizer_18-0.1.1-3PIGSTY.el9.aarch64.rpm
`pg_tokenizer_18`	`0.1.1`	el10.x86_64	pigsty	12.4 MiB	pg_tokenizer_18-0.1.1-3PIGSTY.el10.x86_64.rpm
`pg_tokenizer_18`	`0.1.1`	el10.aarch64	pigsty	12.3 MiB	pg_tokenizer_18-0.1.1-3PIGSTY.el10.aarch64.rpm
`postgresql-18-pg-tokenizer`	`0.1.1`	d12.x86_64	pigsty	11.1 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~bookworm_amd64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	d12.aarch64	pigsty	10.9 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~bookworm_arm64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	d13.x86_64	pigsty	11.1 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~trixie_amd64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	d13.aarch64	pigsty	10.9 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~trixie_arm64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	u22.x86_64	pigsty	12.2 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~jammy_amd64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	u22.aarch64	pigsty	12.0 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~jammy_arm64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	u24.x86_64	pigsty	12.1 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~noble_amd64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	u24.aarch64	pigsty	12.0 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~noble_arm64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	u26.x86_64	pigsty	12.1 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~resolute_amd64.deb
`postgresql-18-pg-tokenizer`	`0.1.1`	u26.aarch64	pigsty	12.0 MiB	postgresql-18-pg-tokenizer_0.1.1-3PIGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pg_tokenizer_17`	`0.1.1`	el8.x86_64	pigsty	13.3 MiB	pg_tokenizer_17-0.1.1-3PIGSTY.el8.x86_64.rpm
`pg_tokenizer_17`	`0.1.1`	el8.aarch64	pigsty	13.0 MiB	pg_tokenizer_17-0.1.1-3PIGSTY.el8.aarch64.rpm
`pg_tokenizer_17`	`0.1.1`	el9.x86_64	pigsty	12.5 MiB	pg_tokenizer_17-0.1.1-3PIGSTY.el9.x86_64.rpm
`pg_tokenizer_17`	`0.1.1`	el9.aarch64	pigsty	12.4 MiB	pg_tokenizer_17-0.1.1-3PIGSTY.el9.aarch64.rpm
`pg_tokenizer_17`	`0.1.1`	el10.x86_64	pigsty	12.4 MiB	pg_tokenizer_17-0.1.1-3PIGSTY.el10.x86_64.rpm
`pg_tokenizer_17`	`0.1.1`	el10.aarch64	pigsty	12.3 MiB	pg_tokenizer_17-0.1.1-3PIGSTY.el10.aarch64.rpm
`postgresql-17-pg-tokenizer`	`0.1.1`	d12.x86_64	pigsty	11.1 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~bookworm_amd64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	d12.aarch64	pigsty	10.9 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~bookworm_arm64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	d13.x86_64	pigsty	11.1 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~trixie_amd64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	d13.aarch64	pigsty	10.9 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~trixie_arm64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	u22.x86_64	pigsty	12.2 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~jammy_amd64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	u22.aarch64	pigsty	12.0 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~jammy_arm64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	u24.x86_64	pigsty	12.1 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~noble_amd64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	u24.aarch64	pigsty	12.0 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~noble_arm64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	u26.x86_64	pigsty	12.1 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~resolute_amd64.deb
`postgresql-17-pg-tokenizer`	`0.1.1`	u26.aarch64	pigsty	12.0 MiB	postgresql-17-pg-tokenizer_0.1.1-3PIGSTY~resolute_arm64.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`pg_tokenizer_16`	`0.1.1`	el8.x86_64	pigsty	13.3 MiB	pg_tokenizer_16-0.1.1-3PIGSTY.el8.x86_64.rpm
`pg_tokenizer_16`	`0.1.1`	el8.aarch64	pigsty	13.0 MiB	pg_tokenizer_16-0.1.1-3PIGSTY.el8.aarch64.rpm
`pg_tokenizer_16`	`0.1.1`	el9.x86_64	pigsty	12.5 MiB	pg_tokenizer_16-0.1.1-3PIGSTY.el9.x86_64.rpm
`pg_tokenizer_16`	`0.1.1`	el9.aarch64	pigsty	12.4 MiB	pg_tokenizer_16-0.1.1-3PIGSTY.el9.aarch64.rpm
`pg_tokenizer_16`	`0.1.1`	el10.x86_64	pigsty	12.4 MiB	pg_tokenizer_16-0.1.1-3PIGSTY.el10.x86_64.rpm
`pg_tokenizer_16`	`0.1.1`	el10.aarch64	pigsty	12.3 MiB	pg_tokenizer_16-0.1.1-3PIGSTY.el10.aarch64.rpm
`postgresql-16-pg-tokenizer`	`0.1.1`	d12.x86_64	pigsty	11.1 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~bookworm_amd64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	d12.aarch64	pigsty	10.9 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~bookworm_arm64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	d13.x86_64	pigsty	11.1 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~trixie_amd64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	d13.aarch64	pigsty	10.9 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~trixie_arm64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	u22.x86_64	pigsty	12.2 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~jammy_amd64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	u22.aarch64	pigsty	12.0 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~jammy_arm64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	u24.x86_64	pigsty	12.1 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~noble_amd64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	u24.aarch64	pigsty	12.0 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~noble_arm64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	u26.x86_64	pigsty	12.1 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~resolute_amd64.deb
`postgresql-16-pg-tokenizer`	`0.1.1`	u26.aarch64	pigsty	12.0 MiB	postgresql-16-pg-tokenizer_0.1.1-3PIGSTY~resolute_arm64.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`pg_tokenizer_15`	`0.1.1`	el8.x86_64	pigsty	13.3 MiB	pg_tokenizer_15-0.1.1-3PIGSTY.el8.x86_64.rpm
`pg_tokenizer_15`	`0.1.1`	el8.aarch64	pigsty	13.0 MiB	pg_tokenizer_15-0.1.1-3PIGSTY.el8.aarch64.rpm
`pg_tokenizer_15`	`0.1.1`	el9.x86_64	pigsty	12.5 MiB	pg_tokenizer_15-0.1.1-3PIGSTY.el9.x86_64.rpm
`pg_tokenizer_15`	`0.1.1`	el9.aarch64	pigsty	12.4 MiB	pg_tokenizer_15-0.1.1-3PIGSTY.el9.aarch64.rpm
`pg_tokenizer_15`	`0.1.1`	el10.x86_64	pigsty	12.3 MiB	pg_tokenizer_15-0.1.1-3PIGSTY.el10.x86_64.rpm
`pg_tokenizer_15`	`0.1.1`	el10.aarch64	pigsty	12.3 MiB	pg_tokenizer_15-0.1.1-3PIGSTY.el10.aarch64.rpm
`postgresql-15-pg-tokenizer`	`0.1.1`	d12.x86_64	pigsty	11.1 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~bookworm_amd64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	d12.aarch64	pigsty	10.9 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~bookworm_arm64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	d13.x86_64	pigsty	11.1 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~trixie_amd64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	d13.aarch64	pigsty	10.9 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~trixie_arm64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	u22.x86_64	pigsty	12.1 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~jammy_amd64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	u22.aarch64	pigsty	12.0 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~jammy_arm64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	u24.x86_64	pigsty	12.1 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~noble_amd64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	u24.aarch64	pigsty	12.0 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~noble_arm64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	u26.x86_64	pigsty	12.1 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~resolute_amd64.deb
`postgresql-15-pg-tokenizer`	`0.1.1`	u26.aarch64	pigsty	12.0 MiB	postgresql-15-pg-tokenizer_0.1.1-3PIGSTY~resolute_arm64.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`pg_tokenizer_14`	`0.1.1`	el8.x86_64	pigsty	13.3 MiB	pg_tokenizer_14-0.1.1-3PIGSTY.el8.x86_64.rpm
`pg_tokenizer_14`	`0.1.1`	el8.aarch64	pigsty	13.0 MiB	pg_tokenizer_14-0.1.1-3PIGSTY.el8.aarch64.rpm
`pg_tokenizer_14`	`0.1.1`	el9.x86_64	pigsty	12.4 MiB	pg_tokenizer_14-0.1.1-3PIGSTY.el9.x86_64.rpm
`pg_tokenizer_14`	`0.1.1`	el9.aarch64	pigsty	12.4 MiB	pg_tokenizer_14-0.1.1-3PIGSTY.el9.aarch64.rpm
`pg_tokenizer_14`	`0.1.1`	el10.x86_64	pigsty	12.3 MiB	pg_tokenizer_14-0.1.1-3PIGSTY.el10.x86_64.rpm
`pg_tokenizer_14`	`0.1.1`	el10.aarch64	pigsty	12.3 MiB	pg_tokenizer_14-0.1.1-3PIGSTY.el10.aarch64.rpm
`postgresql-14-pg-tokenizer`	`0.1.1`	d12.x86_64	pigsty	11.1 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~bookworm_amd64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	d12.aarch64	pigsty	10.9 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~bookworm_arm64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	d13.x86_64	pigsty	11.1 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~trixie_amd64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	d13.aarch64	pigsty	10.9 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~trixie_arm64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	u22.x86_64	pigsty	12.2 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~jammy_amd64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	u22.aarch64	pigsty	12.0 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~jammy_arm64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	u24.x86_64	pigsty	12.1 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~noble_amd64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	u24.aarch64	pigsty	12.0 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~noble_arm64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	u26.x86_64	pigsty	12.1 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~resolute_amd64.deb
`postgresql-14-pg-tokenizer`	`0.1.1`	u26.aarch64	pigsty	12.0 MiB	postgresql-14-pg-tokenizer_0.1.1-3PIGSTY~resolute_arm64.deb

Source

Repository

github.com/tensorchord/pg_tokenizer.rs

Source Tarball

pg_tokenizer.rs-0.1.1.tar.gz

pig build pkg pg_tokenizer;		# 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_tokenizer;		# install via package name, for the active PG version

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

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_tokenizer';

Create this extension with:

CREATE EXTENSION pg_tokenizer;

Usage

GitHub: tensorchord/pg_tokenizer.rs

pg_tokenizer is a PostgreSQL extension that provides tokenizers for full-text search. It is designed to work with VectorChord-bm25 for native BM25 ranking index support.

Quick Start

CREATE EXTENSION pg_tokenizer;

-- Create a tokenizer using the LLMLingua2 model
SELECT create_tokenizer('tokenizer1', $$
model = "llmlingua2"
$$);

-- Tokenize text
SELECT tokenize('PostgreSQL is a powerful, open-source object-relational database system. It has over 15 years of active development.', 'tokenizer1');

Tokenizer Models

pg_tokenizer supports multiple tokenizer models for different languages and use cases:

Model	Language	Description
`llmlingua2`	English	BERT-based tokenizer from LLMLingua2
`jieba`	Chinese	Jieba Chinese text segmentation
`lindera/ipadic`	Japanese	Lindera tokenizer with IPADIC dictionary
Custom models	Any	User-trained models for domain-specific text

Creating Tokenizers

-- English tokenizer
SELECT create_tokenizer('en_tokenizer', $$
model = "llmlingua2"
$$);

-- Chinese tokenizer
SELECT create_tokenizer('zh_tokenizer', $$
model = "jieba"
$$);

-- Japanese tokenizer
SELECT create_tokenizer('ja_tokenizer', $$
model = "lindera/ipadic"
$$);

Tokenizing Text

-- Tokenize English text
SELECT tokenize('full text search in PostgreSQL', 'en_tokenizer');

-- Tokenize Chinese text
SELECT tokenize('PostgreSQL是一个强大的数据库系统', 'zh_tokenizer');

Text Analyzer

pg_tokenizer also provides text analyzer functionality that combines tokenization with additional text processing steps. For detailed text analyzer usage, refer to the Text Analyzer documentation.

Integration with VectorChord-BM25

pg_tokenizer is typically used together with VectorChord-BM25 for full BM25 ranking support:

CREATE EXTENSION IF NOT EXISTS pg_tokenizer CASCADE;
CREATE EXTENSION IF NOT EXISTS vchord_bm25 CASCADE;

-- Create a tokenizer
SELECT create_tokenizer('my_tokenizer', $$
model = "llmlingua2"
$$);

-- Tokenize text into bm25vectors for indexing and search
SELECT tokenize('your search query', 'my_tokenizer');

Documentation

For more details, see the full documentation:

psql_bm25s

Mon, 01 Jan 0001 00:00:00 +0000

psql_bm25s : PostgreSQL extension for BM25-family lexical retrieval

Overview

ID	Extension	Package	Version	Category	License	Language
2210	psql_bm25s	psql_bm25s	`0.4.13`	FTS	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d--	No	Yes	No	Yes	no	no

Relationships
See Also	pg_search pgroonga pg_textsearch pg_fts vchord_bm25 pg_bestmatch pg_tokenizer pg_rrf pgcontext vectorize

Supports PostgreSQL 17-18; optional shared_preload_libraries arena is not required for normal use.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.4.13`	18 17 16 15 14	`psql_bm25s`	-
RPM	PIGSTY	`0.4.13`	18 17 16 15 14	`psql_bm25s_$v`	-
DEB	PIGSTY	`0.4.13`	18 17 16 15 14	`postgresql-$v-psql-bm25s`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
el8.aarch64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
el9.x86_64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
el9.aarch64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
el10.x86_64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
el10.aarch64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
d12.x86_64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
d12.aarch64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
d13.x86_64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
d13.aarch64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
u22.x86_64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
u22.aarch64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
u24.x86_64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
u24.aarch64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
u26.x86_64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A
u26.aarch64	PIGSTY 0.4.13	PIGSTY 0.4.13	N/A	N/A	N/A

PG18

Package	Version	OS	ORG	SIZE	File URL
`psql_bm25s_18`	`0.4.13`	el8.x86_64	pigsty	244.2 KiB	psql_bm25s_18-0.4.13-1PIGSTY.el8.x86_64.rpm
`psql_bm25s_18`	`0.4.13`	el8.aarch64	pigsty	229.7 KiB	psql_bm25s_18-0.4.13-1PIGSTY.el8.aarch64.rpm
`psql_bm25s_18`	`0.4.13`	el9.x86_64	pigsty	231.9 KiB	psql_bm25s_18-0.4.13-1PIGSTY.el9.x86_64.rpm
`psql_bm25s_18`	`0.4.13`	el9.aarch64	pigsty	221.3 KiB	psql_bm25s_18-0.4.13-1PIGSTY.el9.aarch64.rpm
`psql_bm25s_18`	`0.4.13`	el10.x86_64	pigsty	239.2 KiB	psql_bm25s_18-0.4.13-1PIGSTY.el10.x86_64.rpm
`psql_bm25s_18`	`0.4.13`	el10.aarch64	pigsty	227.1 KiB	psql_bm25s_18-0.4.13-1PIGSTY.el10.aarch64.rpm
`postgresql-18-psql-bm25s`	`0.4.13`	d12.x86_64	pigsty	497.3 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~bookworm_amd64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	d12.aarch64	pigsty	475.9 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~bookworm_arm64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	d13.x86_64	pigsty	499.7 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~trixie_amd64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	d13.aarch64	pigsty	479.1 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~trixie_arm64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	u22.x86_64	pigsty	527.1 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~jammy_amd64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	u22.aarch64	pigsty	511.5 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~jammy_arm64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	u24.x86_64	pigsty	510.3 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~noble_amd64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	u24.aarch64	pigsty	497.3 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~noble_arm64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	u26.x86_64	pigsty	506.9 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~resolute_amd64.deb
`postgresql-18-psql-bm25s`	`0.4.13`	u26.aarch64	pigsty	492.8 KiB	postgresql-18-psql-bm25s_0.4.13-1PIGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`psql_bm25s_17`	`0.4.13`	el8.x86_64	pigsty	244.3 KiB	psql_bm25s_17-0.4.13-1PIGSTY.el8.x86_64.rpm
`psql_bm25s_17`	`0.4.13`	el8.aarch64	pigsty	229.7 KiB	psql_bm25s_17-0.4.13-1PIGSTY.el8.aarch64.rpm
`psql_bm25s_17`	`0.4.13`	el9.x86_64	pigsty	231.8 KiB	psql_bm25s_17-0.4.13-1PIGSTY.el9.x86_64.rpm
`psql_bm25s_17`	`0.4.13`	el9.aarch64	pigsty	221.3 KiB	psql_bm25s_17-0.4.13-1PIGSTY.el9.aarch64.rpm
`psql_bm25s_17`	`0.4.13`	el10.x86_64	pigsty	239.1 KiB	psql_bm25s_17-0.4.13-1PIGSTY.el10.x86_64.rpm
`psql_bm25s_17`	`0.4.13`	el10.aarch64	pigsty	227.1 KiB	psql_bm25s_17-0.4.13-1PIGSTY.el10.aarch64.rpm
`postgresql-17-psql-bm25s`	`0.4.13`	d12.x86_64	pigsty	497.2 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~bookworm_amd64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	d12.aarch64	pigsty	475.6 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~bookworm_arm64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	d13.x86_64	pigsty	499.3 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~trixie_amd64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	d13.aarch64	pigsty	479.1 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~trixie_arm64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	u22.x86_64	pigsty	553.4 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~jammy_amd64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	u22.aarch64	pigsty	538.1 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~jammy_arm64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	u24.x86_64	pigsty	510.2 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~noble_amd64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	u24.aarch64	pigsty	497.3 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~noble_arm64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	u26.x86_64	pigsty	506.9 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~resolute_amd64.deb
`postgresql-17-psql-bm25s`	`0.4.13`	u26.aarch64	pigsty	492.7 KiB	postgresql-17-psql-bm25s_0.4.13-1PIGSTY~resolute_arm64.deb

Source

Repository

github.com/Intelligent-Internet/psql_bm25s

Source Tarball

psql_bm25s-0.4.13.tar.gz

pig build pkg psql_bm25s;		# 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 psql_bm25s;		# install via package name, for the active PG version

pig install psql_bm25s -v 18;   # install for PG 18
pig install psql_bm25s -v 17;   # install for PG 17

Create this extension with:

CREATE EXTENSION psql_bm25s;

Usage

Sources: README v0.4.13, API reference, query semantics, input types, index parameters, index policy

psql_bm25s is a PostgreSQL-native index access method for BM25-family lexical retrieval. It keeps the BM25 contract explicit through corpus-statistics-driven ranking, exact top-k retrieval APIs, and PostgreSQL storage/maintenance behavior for mutable tables.

Version 0.4.13 is packaged for PostgreSQL 17 and 18 in this catalog.

Basic Search

CREATE EXTENSION psql_bm25s;

CREATE TABLE docs (
    id integer PRIMARY KEY,
    title text NOT NULL,
    body text NOT NULL
);

INSERT INTO docs (id, title, body) VALUES
    (1, 'red apple', 'fresh red apple fruit'),
    (2, 'green apple', 'green apple slices'),
    (3, 'orange citrus', 'orange citrus fruit'),
    (4, 'cat guide', 'small cat animal care');

CREATE INDEX docs_bm25_idx
    ON docs USING psql_bm25s (body);

SELECT d.id, d.title, h.score
FROM psql_bm25s_query(
    'docs_bm25_idx'::regclass,
    'apple fruit',
    5
) AS h
JOIN docs AS d ON d.ctid = h.ctid
ORDER BY h.score DESC, d.id;

With no WITH (...) options, the index uses Lucene-style BM25 and IDF defaults with the realtime consistency policy.

Indexed Inputs

psql_bm25s supports five indexed source-column types:

text and varchar for direct indexing of ordinary scalar text columns.
text[] and varchar[] for application-owned token streams.
int4[] for applications that manage token IDs externally.

Scalar text and varchar columns are tokenized at the index boundary. Pretokenized arrays avoid scalar retokenization and are the preferred shape when the application already owns tokenization.

Retrieval APIs

The canonical exact BM25 APIs are:

psql_bm25s_query_tokens(regclass, text[], k, weight_mask) for token-text indexes.
psql_bm25s_query_ids(regclass, int4[], k, weight_mask) for token-ID indexes.

The main SQL convenience APIs are:

psql_bm25s_query(regclass, query_text, k, weight_mask, ...)
psql_bm25s_prepared_query(regclass, query_text, ...)
psql_bm25s_query_prepared(prepared_query, k, weight_mask)

These rowset APIs return psql_bm25s_result_hit rows with ctid, doc_id, and score. Join hits back to application rows with ctid when the query needs both row data and the query-time score.

Operators

The operator surface is useful for SQL-native filtering and ordering:

tokens @@ 'query text' is a boolean document-match predicate.
tokens @@@ psql_bm25s_prepared_query(...) is an index-bound prepared predicate.
ORDER BY tokens <=> psql_bm25s_order_tokens(...) ASC LIMIT k is the ordered retrieval form.

@@ is not a ranking API. <=> aligns with true BM25 ordering only when PostgreSQL chooses a real psql_bm25s index scan; use the rowset retrieval APIs when you need the clearest exact top-k contract.

WITH rq AS (
    SELECT psql_bm25s_ranked_query(
        'docs_bm25_idx'::regclass,
        'apple fruit',
        10
    ) AS q
)
SELECT d.*
FROM docs AS d, rq
WHERE d.body @@@ psql_bm25s_filter_query(rq.q)
ORDER BY d.body <=> psql_bm25s_order_tokens(rq.q) ASC
LIMIT (rq.q).k;

Index Options

Scoring reloptions include:

method and idf_method, defaulting to lucene; supported variants are robertson, lucene, atire, bm25l, and bm25+.
k1, default 1.5.
b, default 0.75.
delta, default 0.5, used by BM25L and BM25+.

Scalar text processing reloptions include:

text_lowercase, default true.
text_stopwords, default NULL.
text_stem_english, default false.
text_fold_diacritics, default false.

CREATE INDEX docs_body_bm25_idx
    ON docs USING psql_bm25s (body)
    WITH (
        method = 'lucene',
        idf_method = 'lucene',
        k1 = 1.5,
        b = 0.75,
        text_stem_english = true
    );

Multi-Field and Hybrid Search

For separate title, abstract, and body indexes, use late fusion helpers so each field produces query-scoped hits before scores are combined:

SELECT d.id, d.title, h.score
FROM psql_bm25s_fusion_query(
    ARRAY[
        'docs_title_bm25_idx'::regclass,
        'docs_body_bm25_idx'::regclass
    ],
    'apple fruit',
    ARRAY[3.0, 1.0]::real[],
    10,
    30,
    NULL
) AS h
JOIN docs AS d ON d.ctid = h.ctid
ORDER BY h.score DESC, d.id;

Hybrid vector/BM25 search is also a late-fusion layer. BM25 and vector indexes produce candidates independently, and psql_bm25s_hybrid_fuse_candidates(...) combines them using rrf by default. The core extension does not require pgvector, VectorChord, or any vector type to be installed.

Maintenance and Cache

The public maintenance switch is the consistency reloption:

realtime, the default, keeps committed writes searchable immediately.
eventual favors foreground read/write latency and allows short-term stale BM25 results while maintenance converges.
manual leaves refresh under explicit operator or scheduler control.

Operational helpers include:

psql_bm25s_index_details(regclass)
psql_bm25s_index_policy_recommend(regclass, profile)
psql_bm25s_index_refresh(regclass)
psql_bm25s_index_maintain(regclass)
psql_bm25s_index_try_maintain(regclass)
psql_bm25s_index_maintain_due(max_indexes)

Large immutable index payloads can use a shared generation cache. The zero-configuration DSM cache does not require shared_preload_libraries. For large connection-pool deployments, an optional shared-preload arena can be enabled with shared_preload_libraries = 'psql_bm25s' and psql_bm25s.shared_generation_cache_size, but that arena is not required for normal use.

Related global GUCs include:

psql_bm25s.maintenance_worker_limit
psql_bm25s.preload_timer_interval_ms
psql_bm25s.maintenance_timer_interval_ms
psql_bm25s.maintenance_rebuild_memory_budget

Caveats

The extension is not relocatable after creation; choose a non-public schema at CREATE EXTENSION time if needed.
eventual and manual consistency deliberately trade immediate freshness for lower foreground cost or explicit refresh control.
Logical replication follows PostgreSQL behavior: table rows replicate, but index relations do not replicate as logical data objects, so indexes should be created or rebuilt on subscribers.
The optional shared-preload cache requires PostgreSQL configuration and a restart because the shared arena is allocated at server start.

pg_clickhouse

Mon, 01 Jan 0001 00:00:00 +0000

pg_clickhouse : Interfaces to query ClickHouse databases from PostgreSQL

Overview

ID	Extension	Package	Version	Category	License	Language
2460	pg_clickhouse	pg_clickhouse	`0.10.0`	OLAP	Apache-2.0	C++

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d-r	No	Yes	No	Yes	yes	no

Relationships
See Also	pg_stat_ch duckdb_fdw pg_duckdb pg_mooncake pg_ducklake pg_lake hdfs_fdw kafka_fdw aws_s3 pg_parquet

Release v0.10.0, control SQL version 0.10; preloading is optional; no llvmjit subpackage on el9.x86_64 in the 2026-08-12 build.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`0.10.0`	18 17 16 15 14	`pg_clickhouse`	-
RPM	PIGSTY	`0.10.0`	18 17 16 15 14	`pg_clickhouse_$v`	`openssl`, `libcurl`, `libuuid`, `lz4-libs`, `libzstd`
DEB	PIGSTY	`0.10.0`	18 17 16 15 14	`postgresql-$v-clickhouse`	`libssl3

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
el8.aarch64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
el9.x86_64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
el9.aarch64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
el10.x86_64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
el10.aarch64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
d12.x86_64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
d12.aarch64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
d13.x86_64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
d13.aarch64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
u22.x86_64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
u22.aarch64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
u24.x86_64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
u24.aarch64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
u26.x86_64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0
u26.aarch64	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0	PIGSTY 0.10.0

PG18

Package	Version	OS	ORG	SIZE	File URL
`pg_clickhouse_18`	`0.10.0`	el8.x86_64	pigsty	169.8 KiB	pg_clickhouse_18-0.10.0-1PIGSTY.el8.x86_64.rpm
`pg_clickhouse_18`	`0.10.0`	el8.aarch64	pigsty	167.9 KiB	pg_clickhouse_18-0.10.0-1PIGSTY.el8.aarch64.rpm
`pg_clickhouse_18`	`0.10.0`	el9.x86_64	pigsty	165.7 KiB	pg_clickhouse_18-0.10.0-1PIGSTY.el9.x86_64.rpm
`pg_clickhouse_18`	`0.10.0`	el9.aarch64	pigsty	162.4 KiB	pg_clickhouse_18-0.10.0-1PIGSTY.el9.aarch64.rpm
`pg_clickhouse_18`	`0.10.0`	el10.x86_64	pigsty	162.8 KiB	pg_clickhouse_18-0.10.0-1PIGSTY.el10.x86_64.rpm
`pg_clickhouse_18`	`0.10.0`	el10.aarch64	pigsty	165.2 KiB	pg_clickhouse_18-0.10.0-1PIGSTY.el10.aarch64.rpm
`postgresql-18-clickhouse`	`0.10.0`	d12.x86_64	pigsty	446.5 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~bookworm_amd64.deb
`postgresql-18-clickhouse`	`0.10.0`	d12.aarch64	pigsty	439.9 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~bookworm_arm64.deb
`postgresql-18-clickhouse`	`0.10.0`	d13.x86_64	pigsty	447.6 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~trixie_amd64.deb
`postgresql-18-clickhouse`	`0.10.0`	d13.aarch64	pigsty	442.4 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~trixie_arm64.deb
`postgresql-18-clickhouse`	`0.10.0`	u22.x86_64	pigsty	467.8 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~jammy_amd64.deb
`postgresql-18-clickhouse`	`0.10.0`	u22.aarch64	pigsty	468.8 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~jammy_arm64.deb
`postgresql-18-clickhouse`	`0.10.0`	u24.x86_64	pigsty	446.7 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~noble_amd64.deb
`postgresql-18-clickhouse`	`0.10.0`	u24.aarch64	pigsty	449.1 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~noble_arm64.deb
`postgresql-18-clickhouse`	`0.10.0`	u26.x86_64	pigsty	444.4 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~resolute_amd64.deb
`postgresql-18-clickhouse`	`0.10.0`	u26.aarch64	pigsty	445.8 KiB	postgresql-18-clickhouse_0.10.0-1PGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pg_clickhouse_17`	`0.10.0`	el8.x86_64	pigsty	169.7 KiB	pg_clickhouse_17-0.10.0-1PIGSTY.el8.x86_64.rpm
`pg_clickhouse_17`	`0.10.0`	el8.aarch64	pigsty	167.9 KiB	pg_clickhouse_17-0.10.0-1PIGSTY.el8.aarch64.rpm
`pg_clickhouse_17`	`0.10.0`	el9.x86_64	pigsty	165.6 KiB	pg_clickhouse_17-0.10.0-1PIGSTY.el9.x86_64.rpm
`pg_clickhouse_17`	`0.10.0`	el9.aarch64	pigsty	162.3 KiB	pg_clickhouse_17-0.10.0-1PIGSTY.el9.aarch64.rpm
`pg_clickhouse_17`	`0.10.0`	el10.x86_64	pigsty	162.8 KiB	pg_clickhouse_17-0.10.0-1PIGSTY.el10.x86_64.rpm
`pg_clickhouse_17`	`0.10.0`	el10.aarch64	pigsty	164.9 KiB	pg_clickhouse_17-0.10.0-1PIGSTY.el10.aarch64.rpm
`postgresql-17-clickhouse`	`0.10.0`	d12.x86_64	pigsty	446.6 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~bookworm_amd64.deb
`postgresql-17-clickhouse`	`0.10.0`	d12.aarch64	pigsty	439.8 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~bookworm_arm64.deb
`postgresql-17-clickhouse`	`0.10.0`	d13.x86_64	pigsty	447.4 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~trixie_amd64.deb
`postgresql-17-clickhouse`	`0.10.0`	d13.aarch64	pigsty	442.0 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~trixie_arm64.deb
`postgresql-17-clickhouse`	`0.10.0`	u22.x86_64	pigsty	524.4 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~jammy_amd64.deb
`postgresql-17-clickhouse`	`0.10.0`	u22.aarch64	pigsty	525.1 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~jammy_arm64.deb
`postgresql-17-clickhouse`	`0.10.0`	u24.x86_64	pigsty	446.6 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~noble_amd64.deb
`postgresql-17-clickhouse`	`0.10.0`	u24.aarch64	pigsty	448.6 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~noble_arm64.deb
`postgresql-17-clickhouse`	`0.10.0`	u26.x86_64	pigsty	444.1 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~resolute_amd64.deb
`postgresql-17-clickhouse`	`0.10.0`	u26.aarch64	pigsty	445.6 KiB	postgresql-17-clickhouse_0.10.0-1PGSTY~resolute_arm64.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`pg_clickhouse_16`	`0.10.0`	el8.x86_64	pigsty	169.6 KiB	pg_clickhouse_16-0.10.0-1PIGSTY.el8.x86_64.rpm
`pg_clickhouse_16`	`0.10.0`	el8.aarch64	pigsty	167.8 KiB	pg_clickhouse_16-0.10.0-1PIGSTY.el8.aarch64.rpm
`pg_clickhouse_16`	`0.10.0`	el9.x86_64	pigsty	165.4 KiB	pg_clickhouse_16-0.10.0-1PIGSTY.el9.x86_64.rpm
`pg_clickhouse_16`	`0.10.0`	el9.aarch64	pigsty	162.1 KiB	pg_clickhouse_16-0.10.0-1PIGSTY.el9.aarch64.rpm
`pg_clickhouse_16`	`0.10.0`	el10.x86_64	pigsty	162.2 KiB	pg_clickhouse_16-0.10.0-1PIGSTY.el10.x86_64.rpm
`pg_clickhouse_16`	`0.10.0`	el10.aarch64	pigsty	164.8 KiB	pg_clickhouse_16-0.10.0-1PIGSTY.el10.aarch64.rpm
`postgresql-16-clickhouse`	`0.10.0`	d12.x86_64	pigsty	446.2 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~bookworm_amd64.deb
`postgresql-16-clickhouse`	`0.10.0`	d12.aarch64	pigsty	439.7 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~bookworm_arm64.deb
`postgresql-16-clickhouse`	`0.10.0`	d13.x86_64	pigsty	447.1 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~trixie_amd64.deb
`postgresql-16-clickhouse`	`0.10.0`	d13.aarch64	pigsty	441.6 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~trixie_arm64.deb
`postgresql-16-clickhouse`	`0.10.0`	u22.x86_64	pigsty	519.3 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~jammy_amd64.deb
`postgresql-16-clickhouse`	`0.10.0`	u22.aarch64	pigsty	520.3 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~jammy_arm64.deb
`postgresql-16-clickhouse`	`0.10.0`	u24.x86_64	pigsty	446.2 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~noble_amd64.deb
`postgresql-16-clickhouse`	`0.10.0`	u24.aarch64	pigsty	448.2 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~noble_arm64.deb
`postgresql-16-clickhouse`	`0.10.0`	u26.x86_64	pigsty	443.6 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~resolute_amd64.deb
`postgresql-16-clickhouse`	`0.10.0`	u26.aarch64	pigsty	445.2 KiB	postgresql-16-clickhouse_0.10.0-1PGSTY~resolute_arm64.deb

PG15

Package	Version	OS	ORG	SIZE	File URL
`pg_clickhouse_15`	`0.10.0`	el8.x86_64	pigsty	173.3 KiB	pg_clickhouse_15-0.10.0-1PIGSTY.el8.x86_64.rpm
`pg_clickhouse_15`	`0.10.0`	el8.aarch64	pigsty	170.9 KiB	pg_clickhouse_15-0.10.0-1PIGSTY.el8.aarch64.rpm
`pg_clickhouse_15`	`0.10.0`	el9.x86_64	pigsty	168.5 KiB	pg_clickhouse_15-0.10.0-1PIGSTY.el9.x86_64.rpm
`pg_clickhouse_15`	`0.10.0`	el9.aarch64	pigsty	170.9 KiB	pg_clickhouse_15-0.10.0-1PIGSTY.el9.aarch64.rpm
`pg_clickhouse_15`	`0.10.0`	el10.x86_64	pigsty	171.1 KiB	pg_clickhouse_15-0.10.0-1PIGSTY.el10.x86_64.rpm
`pg_clickhouse_15`	`0.10.0`	el10.aarch64	pigsty	173.8 KiB	pg_clickhouse_15-0.10.0-1PIGSTY.el10.aarch64.rpm
`postgresql-15-clickhouse`	`0.10.0`	d12.x86_64	pigsty	449.7 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~bookworm_amd64.deb
`postgresql-15-clickhouse`	`0.10.0`	d12.aarch64	pigsty	442.3 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~bookworm_arm64.deb
`postgresql-15-clickhouse`	`0.10.0`	d13.x86_64	pigsty	450.6 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~trixie_amd64.deb
`postgresql-15-clickhouse`	`0.10.0`	d13.aarch64	pigsty	444.9 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~trixie_arm64.deb
`postgresql-15-clickhouse`	`0.10.0`	u22.x86_64	pigsty	526.5 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~jammy_amd64.deb
`postgresql-15-clickhouse`	`0.10.0`	u22.aarch64	pigsty	526.7 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~jammy_arm64.deb
`postgresql-15-clickhouse`	`0.10.0`	u24.x86_64	pigsty	453.8 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~noble_amd64.deb
`postgresql-15-clickhouse`	`0.10.0`	u24.aarch64	pigsty	455.4 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~noble_arm64.deb
`postgresql-15-clickhouse`	`0.10.0`	u26.x86_64	pigsty	450.1 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~resolute_amd64.deb
`postgresql-15-clickhouse`	`0.10.0`	u26.aarch64	pigsty	452.9 KiB	postgresql-15-clickhouse_0.10.0-1PGSTY~resolute_arm64.deb

PG14

Package	Version	OS	ORG	SIZE	File URL
`pg_clickhouse_14`	`0.10.0`	el8.x86_64	pigsty	173.1 KiB	pg_clickhouse_14-0.10.0-1PIGSTY.el8.x86_64.rpm
`pg_clickhouse_14`	`0.10.0`	el8.aarch64	pigsty	170.9 KiB	pg_clickhouse_14-0.10.0-1PIGSTY.el8.aarch64.rpm
`pg_clickhouse_14`	`0.10.0`	el9.x86_64	pigsty	168.5 KiB	pg_clickhouse_14-0.10.0-1PIGSTY.el9.x86_64.rpm
`pg_clickhouse_14`	`0.10.0`	el9.aarch64	pigsty	170.9 KiB	pg_clickhouse_14-0.10.0-1PIGSTY.el9.aarch64.rpm
`pg_clickhouse_14`	`0.10.0`	el10.x86_64	pigsty	171.2 KiB	pg_clickhouse_14-0.10.0-1PIGSTY.el10.x86_64.rpm
`pg_clickhouse_14`	`0.10.0`	el10.aarch64	pigsty	173.7 KiB	pg_clickhouse_14-0.10.0-1PIGSTY.el10.aarch64.rpm
`postgresql-14-clickhouse`	`0.10.0`	d12.x86_64	pigsty	449.6 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~bookworm_amd64.deb
`postgresql-14-clickhouse`	`0.10.0`	d12.aarch64	pigsty	442.5 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~bookworm_arm64.deb
`postgresql-14-clickhouse`	`0.10.0`	d13.x86_64	pigsty	450.5 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~trixie_amd64.deb
`postgresql-14-clickhouse`	`0.10.0`	d13.aarch64	pigsty	445.0 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~trixie_arm64.deb
`postgresql-14-clickhouse`	`0.10.0`	u22.x86_64	pigsty	526.4 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~jammy_amd64.deb
`postgresql-14-clickhouse`	`0.10.0`	u22.aarch64	pigsty	526.6 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~jammy_arm64.deb
`postgresql-14-clickhouse`	`0.10.0`	u24.x86_64	pigsty	453.7 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~noble_amd64.deb
`postgresql-14-clickhouse`	`0.10.0`	u24.aarch64	pigsty	455.4 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~noble_arm64.deb
`postgresql-14-clickhouse`	`0.10.0`	u26.x86_64	pigsty	450.0 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~resolute_amd64.deb
`postgresql-14-clickhouse`	`0.10.0`	u26.aarch64	pigsty	452.8 KiB	postgresql-14-clickhouse_0.10.0-1PGSTY~resolute_arm64.deb

Source

Repository

github.com/ClickHouse/pg_clickhouse

Source Tarball

pg_clickhouse-0.10.0.tar.gz

pig build pkg pg_clickhouse;		# 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_clickhouse;		# install via package name, for the active PG version

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

Create this extension with:

CREATE EXTENSION pg_clickhouse;

Usage

Sources:

pg_clickhouse 0.10.0 exposes ClickHouse tables to PostgreSQL through the clickhouse_fdw foreign data wrapper. Upstream targets PostgreSQL 13 or later and ClickHouse 23.3 or later; current Pigsty packages cover PostgreSQL 14–18. No preload is required for normal use; session_preload_libraries and shared_preload_libraries are optional connection-startup optimizations.

Connect PostgreSQL to ClickHouse

CREATE EXTENSION pg_clickhouse;

CREATE SERVER taxi_srv
FOREIGN DATA WRAPPER clickhouse_fdw
OPTIONS (
  driver 'binary',
  host 'localhost',
  dbname 'taxi',
  compression 'lz4'
);

CREATE USER MAPPING FOR CURRENT_USER
SERVER taxi_srv
OPTIONS (user 'default');

CREATE SCHEMA taxi;
IMPORT FOREIGN SCHEMA taxi FROM SERVER taxi_srv INTO taxi;

The required driver option is binary or http. Common server options include host, port, dbname, compression, secure, and min_tls_version; user mappings accept user and password. Version 0.10 deprecates and ignores fetch_size because both drivers now stream the same Native format.

IMPORT FOREIGN SCHEMA supports LIMIT TO (...) and EXCEPT (...). Imported mixed-case identifiers remain quoted and must be referenced with matching quotes.

Query and Write Foreign Tables

EXPLAIN (VERBOSE)
SELECT node_id, count(*)
FROM taxi.logs
GROUP BY node_id;

INSERT INTO taxi.nodes(node_id, name)
VALUES (9, 'west-node');

COPY taxi.nodes(node_id, name) FROM STDIN;

SELECT, EXPLAIN, prepared statements, INSERT, and COPY operate on foreign tables. In version 0.10 the binary driver flushes inserts in bounded 64 MiB batches, so COPY is no longer merely expanded into one statement per row. Use EXPLAIN (VERBOSE) to inspect remote SQL and verify which filters, joins, aggregates, and functions were pushed down.

Direct Query and Command APIs

Version 0.10 adds typed arbitrary-query and command interfaces:

GRANT EXECUTE ON FUNCTION clickhouse_query(text, text) TO analyst;
GRANT EXECUTE ON PROCEDURE clickhouse_perform(text, text) TO operator;

SELECT *
FROM clickhouse_query(
  'taxi_srv',
  'SELECT region, count() FROM taxi GROUP BY region'
) AS t(region text, n bigint);

CALL clickhouse_perform(
  'taxi_srv',
  'OPTIMIZE TABLE taxi.nodes FINAL'
);

SELECT clickhouse_server_version('taxi_srv');

clickhouse_query(server, sql) returns rows using the caller-provided column definition, while clickhouse_perform(server, sql) discards any result. Both can run arbitrary remote SQL, so EXECUTE is revoked from PUBLIC and should be granted narrowly. clickhouse_raw_query() is deprecated in favor of these interfaces.

Pushdown and Session Settings

Version 0.10 expands aggregate and function pushdown, improves aggregate execution over mixed local and foreign partitions, and fixes several PostgreSQL NULL-semantics mismatches. Subquery pushdown requires ClickHouse 25.8 or later; older servers evaluate those subqueries locally.

The default pg_clickhouse.session_settings preserves PostgreSQL-compatible behavior, including join_use_nulls = 1, group_by_use_nulls = 1, final = 1, and transform_null_in = 0. If it is overridden, retain the settings needed by the workload—especially transform_null_in = 0, which is required for safe IN pushdown.

Upgrade and Operational Boundaries

ALTER EXTENSION pg_clickhouse UPDATE TO '0.10';
SELECT pgch_version();

The extension SQL version is 0.10, while pgch_version() reports the full library version 0.10.0. An installation upgraded from SQL version 0.3 must run ALTER EXTENSION after the new files are installed.

If pg_clickhouse is placed in session_preload_libraries, new sessions load it automatically. If it is placed in shared_preload_libraries, changing the library requires a PostgreSQL restart. Neither setting is mandatory, unlike extensions that register postmaster hooks.

Lightweight UPDATE and DELETE remain outside the documented write surface. Treat direct remote SQL as privileged, test pushdown with production-shaped NULL and type cases, and validate both PostgreSQL and ClickHouse versions before relying on a version-gated optimization.

pg_orca

Mon, 01 Jan 0001 00:00:00 +0000

pg_orca : ORCA query optimizer as a PostgreSQL extension

Overview

ID	Extension	Package	Version	Category	License	Language
2540	pg_orca	pg_orca	`1.0.0`	OLAP	Apache-2.0	C++

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	No	Yes	Yes	Yes	no	no

Relationships
See Also	pg_hint_plan hypopg index_advisor online_advisor pg_qualstats pg_stat_plans plan_filter pg_track_optimizer pg_strom pg_regresql

PG18 only; use session_preload_libraries=pg_orca for automatic planner hook loading.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`1.0.0`	18 17 16 15 14	`pg_orca`	-
RPM	PIGSTY	`1.0.0`	18 17 16 15 14	`pg_orca_$v`	-
DEB	PIGSTY	`1.0.0`	18 17 16 15 14	`postgresql-$v-pg-orca`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
el8.aarch64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
el9.aarch64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
el10.x86_64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
el10.aarch64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
d12.x86_64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
d12.aarch64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
d13.x86_64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
d13.aarch64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
u22.x86_64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
u22.aarch64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
u24.x86_64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
u24.aarch64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
u26.x86_64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A
u26.aarch64	PIGSTY 1.0.0	N/A	N/A	N/A	N/A

PG18

Package	Version	OS	ORG	SIZE	File URL
`pg_orca_18`	`1.0.0`	el8.x86_64	pigsty	2.2 MiB	pg_orca_18-1.0.0-1PIGSTY.el8.x86_64.rpm
`pg_orca_18`	`1.0.0`	el8.aarch64	pigsty	2.0 MiB	pg_orca_18-1.0.0-1PIGSTY.el8.aarch64.rpm
`pg_orca_18`	`1.0.0`	el9.x86_64	pigsty	2.2 MiB	pg_orca_18-1.0.0-1PIGSTY.el9.x86_64.rpm
`pg_orca_18`	`1.0.0`	el9.aarch64	pigsty	2.0 MiB	pg_orca_18-1.0.0-1PIGSTY.el9.aarch64.rpm
`pg_orca_18`	`1.0.0`	el10.x86_64	pigsty	2.0 MiB	pg_orca_18-1.0.0-1PIGSTY.el10.x86_64.rpm
`pg_orca_18`	`1.0.0`	el10.aarch64	pigsty	1.8 MiB	pg_orca_18-1.0.0-1PIGSTY.el10.aarch64.rpm
`postgresql-18-pg-orca`	`1.0.0`	d12.x86_64	pigsty	1.7 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~bookworm_amd64.deb
`postgresql-18-pg-orca`	`1.0.0`	d12.aarch64	pigsty	1.5 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~bookworm_arm64.deb
`postgresql-18-pg-orca`	`1.0.0`	d13.x86_64	pigsty	1.7 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~trixie_amd64.deb
`postgresql-18-pg-orca`	`1.0.0`	d13.aarch64	pigsty	1.5 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~trixie_arm64.deb
`postgresql-18-pg-orca`	`1.0.0`	u22.x86_64	pigsty	1.7 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~jammy_amd64.deb
`postgresql-18-pg-orca`	`1.0.0`	u22.aarch64	pigsty	1.6 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~jammy_arm64.deb
`postgresql-18-pg-orca`	`1.0.0`	u24.x86_64	pigsty	1.7 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~noble_amd64.deb
`postgresql-18-pg-orca`	`1.0.0`	u24.aarch64	pigsty	1.6 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~noble_arm64.deb
`postgresql-18-pg-orca`	`1.0.0`	u26.x86_64	pigsty	1.7 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~resolute_amd64.deb
`postgresql-18-pg-orca`	`1.0.0`	u26.aarch64	pigsty	1.6 MiB	postgresql-18-pg-orca_1.0.0-1PIGSTY~resolute_arm64.deb

Source

Repository

github.com/quantumiodb/pgorca

Source Tarball

pg_orca-1.0.0.tar.gz

pig build pkg pg_orca;		# 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_orca;		# install via package name, for the active PG version

pig install pg_orca -v 18;   # install for PG 18

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_orca';

Create this extension with:

CREATE EXTENSION pg_orca;

Usage

Sources: pgorca README, entrypoint/GUC source, control file.

pg_orca plugs the ORCA cost-based optimizer from the Greenplum/Apache Cloudberry lineage into a standard PostgreSQL 18 server. The upstream README describes this project as PostgreSQL 18-only, and the local package metadata also marks it for PG18 only.

Enable ORCA For A Session

CREATE EXTENSION loads the library in the current session, so the pg_orca.* GUCs and planner hook are available immediately:

CREATE EXTENSION pg_orca;

SET pg_orca.enable_orca = on;

EXPLAIN
SELECT *
FROM orders
WHERE customer_id = 42
  AND created_at >= now() - interval '30 days';

If ORCA cannot handle a query, the README says it falls back to the standard PostgreSQL planner automatically. Turn on fallback logging while validating a workload:

SET pg_orca.trace_fallback = on;

Preload For New Connections

For automatic planner-hook loading in later sessions, upstream recommends session_preload_libraries, not shared_preload_libraries:

ALTER DATABASE mydb SET session_preload_libraries = 'pg_orca';
ALTER DATABASE mydb SET pg_orca.enable_orca = on;

Existing sessions are unaffected until they reconnect. If another session preload library is already configured, include both values explicitly:

ALTER DATABASE mydb
SET session_preload_libraries = 'pg_orca,pg_stat_statements';

Role-local and cluster-wide scopes are also valid:

ALTER ROLE bench SET session_preload_libraries = 'pg_orca';

ALTER SYSTEM SET session_preload_libraries = 'pg_orca';
SELECT pg_reload_conf();

Tuning And Diagnostics

The README documents these main GUCs:

pg_orca.enable_orca: enable ORCA; default off.
pg_orca.trace_fallback: log fallback to the standard planner; default off.
optimizer_segments: segment count for costing; default 1.
optimizer_sort_factor: sort cost scaling; default 1.0.
optimizer_metadata_caching: cache relation metadata; default on.
optimizer_mdcache_size: metadata cache size in KB; default 16384.
optimizer_search_strategy_path: optional custom search strategy XML path.

The entrypoint source also defines additional ORCA tuning and debug GUCs such as optimizer_join_order, pg_orca.join_order_dynamic_threshold, pg_orca.cost_model, and optimizer_print_*. Treat those as workload/debug knobs and validate plans before keeping them in a persistent database setting.

Caveats

PostgreSQL 18 only.
Use session_preload_libraries = 'pg_orca' for automatic loading in new sessions.
ORCA is disabled by default after loading; set pg_orca.enable_orca = on.
Fallback to the PostgreSQL planner is expected for unsupported queries; enable pg_orca.trace_fallback when checking coverage.

pg_lake

Mon, 01 Jan 0001 00:00:00 +0000

pg_lake : Data lake extension by Snowflake

Overview

ID	Extension	Package	Version	Category	License	Language
2560	pg_lake	pg_lake	`3.4`	OLAP	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	Yes	Yes	Yes	Yes	no	no

Relationships
Schemas	`lake` `pg_catalog`
Requires	pg_lake_copy pg_lake_table
See Also	pg_ducklake pg_duckdb pg_parquet pg_mooncake duckdb_fdw aws_s3 file_fdw pg_bulkload pg_clickhouse columnar
Siblings	pg_extension_base pg_extension_updater pg_map pg_lake_engine pg_lake_iceberg pg_lake_table pg_lake_copy

Pigsty packages this release for PG16-18. Configure shared_preload_libraries=pg_extension_base and run the matching PG-major pgduck_server process. RPM supports EL9/EL10 only; EL8 is rejected because OpenSSL 3 is required. DEB supports Debian 12/13 and Ubuntu 22.04/24.04/26.04 on amd64/arm64. DuckDB and Avro are private per PG major. Co-installation with pg_duckdb, pg_mooncake, and duckdb_fdw is file-safe, but overlapping hooks and COPY behavior can be preload-order-sensitive. Extension SQL/control version is 3.4; source and DEB/RPM package version is 3.4.0.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`3.4`	18 17 16 15 14	`pg_lake`	`pg_lake_copy`, `pg_lake_table`
RPM	PIGSTY	`3.4.0`	18 17 16 15 14	`pg_lake_$v`	-
DEB	PIGSTY	`3.4.0`	18 17 16 15 14	`postgresql-$v-pg-lake`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	N/A	N/A	N/A	N/A	N/A
el8.aarch64	N/A	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el9.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A

PG18

Package	Version	OS	ORG	SIZE	File URL
`pg_lake_18`	`3.4.0`	el9.x86_64	pigsty	19.8 MiB	pg_lake_18-3.4.0-2PIGSTY.el9.x86_64.rpm
`pg_lake_18`	`3.4.0`	el9.aarch64	pigsty	18.2 MiB	pg_lake_18-3.4.0-2PIGSTY.el9.aarch64.rpm
`pg_lake_18`	`3.4.0`	el10.x86_64	pigsty	19.2 MiB	pg_lake_18-3.4.0-2PIGSTY.el10.x86_64.rpm
`pg_lake_18`	`3.4.0`	el10.aarch64	pigsty	17.4 MiB	pg_lake_18-3.4.0-2PIGSTY.el10.aarch64.rpm
`postgresql-18-pg-lake`	`3.4.0`	d12.x86_64	pigsty	19.0 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~bookworm_amd64.deb
`postgresql-18-pg-lake`	`3.4.0`	d12.aarch64	pigsty	16.8 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~bookworm_arm64.deb
`postgresql-18-pg-lake`	`3.4.0`	d13.x86_64	pigsty	20.0 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~trixie_amd64.deb
`postgresql-18-pg-lake`	`3.4.0`	d13.aarch64	pigsty	17.6 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~trixie_arm64.deb
`postgresql-18-pg-lake`	`3.4.0`	u22.x86_64	pigsty	19.4 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~jammy_amd64.deb
`postgresql-18-pg-lake`	`3.4.0`	u22.aarch64	pigsty	18.1 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~jammy_arm64.deb
`postgresql-18-pg-lake`	`3.4.0`	u24.x86_64	pigsty	19.5 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~noble_amd64.deb
`postgresql-18-pg-lake`	`3.4.0`	u24.aarch64	pigsty	18.2 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~noble_arm64.deb
`postgresql-18-pg-lake`	`3.4.0`	u26.x86_64	pigsty	20.0 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~resolute_amd64.deb
`postgresql-18-pg-lake`	`3.4.0`	u26.aarch64	pigsty	18.9 MiB	postgresql-18-pg-lake_3.4.0-2PIGSTY~resolute_arm64.deb

PG17

Package	Version	OS	ORG	SIZE	File URL
`pg_lake_17`	`3.4.0`	el9.x86_64	pigsty	19.9 MiB	pg_lake_17-3.4.0-2PIGSTY.el9.x86_64.rpm
`pg_lake_17`	`3.4.0`	el9.aarch64	pigsty	18.2 MiB	pg_lake_17-3.4.0-2PIGSTY.el9.aarch64.rpm
`pg_lake_17`	`3.4.0`	el10.x86_64	pigsty	19.2 MiB	pg_lake_17-3.4.0-2PIGSTY.el10.x86_64.rpm
`pg_lake_17`	`3.4.0`	el10.aarch64	pigsty	17.3 MiB	pg_lake_17-3.4.0-2PIGSTY.el10.aarch64.rpm
`postgresql-17-pg-lake`	`3.4.0`	d12.x86_64	pigsty	19.0 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~bookworm_amd64.deb
`postgresql-17-pg-lake`	`3.4.0`	d12.aarch64	pigsty	16.8 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~bookworm_arm64.deb
`postgresql-17-pg-lake`	`3.4.0`	d13.x86_64	pigsty	20.0 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~trixie_amd64.deb
`postgresql-17-pg-lake`	`3.4.0`	d13.aarch64	pigsty	17.5 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~trixie_arm64.deb
`postgresql-17-pg-lake`	`3.4.0`	u22.x86_64	pigsty	19.6 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~jammy_amd64.deb
`postgresql-17-pg-lake`	`3.4.0`	u22.aarch64	pigsty	18.3 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~jammy_arm64.deb
`postgresql-17-pg-lake`	`3.4.0`	u24.x86_64	pigsty	19.5 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~noble_amd64.deb
`postgresql-17-pg-lake`	`3.4.0`	u24.aarch64	pigsty	18.2 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~noble_arm64.deb
`postgresql-17-pg-lake`	`3.4.0`	u26.x86_64	pigsty	20.0 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~resolute_amd64.deb
`postgresql-17-pg-lake`	`3.4.0`	u26.aarch64	pigsty	18.8 MiB	postgresql-17-pg-lake_3.4.0-2PIGSTY~resolute_arm64.deb

PG16

Package	Version	OS	ORG	SIZE	File URL
`pg_lake_16`	`3.4.0`	el9.x86_64	pigsty	19.9 MiB	pg_lake_16-3.4.0-2PIGSTY.el9.x86_64.rpm
`pg_lake_16`	`3.4.0`	el9.aarch64	pigsty	18.2 MiB	pg_lake_16-3.4.0-2PIGSTY.el9.aarch64.rpm
`pg_lake_16`	`3.4.0`	el10.x86_64	pigsty	19.2 MiB	pg_lake_16-3.4.0-2PIGSTY.el10.x86_64.rpm
`pg_lake_16`	`3.4.0`	el10.aarch64	pigsty	17.3 MiB	pg_lake_16-3.4.0-2PIGSTY.el10.aarch64.rpm
`postgresql-16-pg-lake`	`3.4.0`	d12.x86_64	pigsty	19.0 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~bookworm_amd64.deb
`postgresql-16-pg-lake`	`3.4.0`	d12.aarch64	pigsty	16.8 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~bookworm_arm64.deb
`postgresql-16-pg-lake`	`3.4.0`	d13.x86_64	pigsty	19.9 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~trixie_amd64.deb
`postgresql-16-pg-lake`	`3.4.0`	d13.aarch64	pigsty	17.5 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~trixie_arm64.deb
`postgresql-16-pg-lake`	`3.4.0`	u22.x86_64	pigsty	19.5 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~jammy_amd64.deb
`postgresql-16-pg-lake`	`3.4.0`	u22.aarch64	pigsty	18.2 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~jammy_arm64.deb
`postgresql-16-pg-lake`	`3.4.0`	u24.x86_64	pigsty	19.5 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~noble_amd64.deb
`postgresql-16-pg-lake`	`3.4.0`	u24.aarch64	pigsty	18.2 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~noble_arm64.deb
`postgresql-16-pg-lake`	`3.4.0`	u26.x86_64	pigsty	20.0 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~resolute_amd64.deb
`postgresql-16-pg-lake`	`3.4.0`	u26.aarch64	pigsty	18.8 MiB	postgresql-16-pg-lake_3.4.0-2PIGSTY~resolute_arm64.deb

Source

Repository

github.com/Snowflake-Labs/pg_lake

Source Tarball

pg_lake-3.4.0.tar.gz

pig build pkg pg_lake;		# 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_lake;		# install via package name, for the active PG version

pig install pg_lake -v 18;   # install for PG 18
pig install pg_lake -v 17;   # install for PG 17
pig install pg_lake -v 16;   # install for PG 16

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_extension_base';

Create this extension with:

CREATE EXTENSION pg_lake CASCADE; -- requires pg_lake_copy, pg_lake_table

Usage

Sources:

pg_lake is the top-level extension for Snowflake’s PostgreSQL lakehouse stack. It installs the table, Iceberg, copy, query-engine, extension-base, and map components needed to query object-store files and create transactional Iceberg tables. The PostgreSQL extensions orchestrate planning and transactions while a separate local pgduck_server process executes vectorized work with DuckDB.

Start the Packaged Stack

Version 3.4 supports PostgreSQL 16 through 18. The PIGSTY RPM and DEB packages install the extension files and a versioned pgduck_server binary, but they do not currently install or auto-start a systemd service. Running CREATE EXTENSION does not start pgduck_server either.

Add pg_extension_base to shared_preload_libraries and restart PostgreSQL:

shared_preload_libraries = 'pg_extension_base'

pgduck_server listens on /tmp/.s.PGSQL.5332 with mode 0770 by default. Run it as the PostgreSQL operating-system user so PostgreSQL can access the socket. Do not start it as an unrelated login user with the bare command.

# Debian/Ubuntu with PostgreSQL 18; use 16 or 17 as appropriate.
PG_LAKE_SERVER=/usr/lib/postgresql/18/bin/pgduck_server
# RHEL-compatible systems use /usr/pgsql-18/bin/pgduck_server.

sudo install -d -o postgres -g postgres -m 0700 \
  /var/lib/pg_lake /var/lib/pg_lake/extensions
sudo install -d -o postgres -g postgres -m 0750 /var/cache/pg_lake
sudo -u postgres -H "$PG_LAKE_SERVER" \
  --duckdb_database_file_path /var/lib/pg_lake/pgduck_server.db \
  --extensions_dir /var/lib/pg_lake/extensions \
  --cache_dir /var/cache/pg_lake

This command runs in the foreground and must remain running. Use a service supervisor for production. If you use a dedicated service account instead, make it a member of the postgres group and start the server with --unix_socket_group postgres --unix_socket_permissions 0770.

In another terminal, verify the query engine before creating the extensions:

sudo -u postgres psql -X \
  "host=/tmp port=5332 dbname=postgres connect_timeout=2" \
  -c 'SELECT version();'

Then create the complete dependency tree in the target database:

CREATE EXTENSION pg_lake CASCADE;
SELECT lake.version();

Configure Object-Store Access

Object-store credentials are resolved by pgduck_server, not by the PostgreSQL backend. AWS and GCP can use their normal credential chains. For a local S3-compatible endpoint such as MinIO, first create the bucket, connect directly to pgduck_server, and create a persistent DuckDB secret:

sudo -u postgres psql -X -h /tmp -p 5332 -d postgres

CREATE PERSISTENT SECRET pglake_object_store (
    TYPE S3,
    KEY_ID 'access-key',
    SECRET 'secret-key',
    REGION 'us-east-1',
    ENDPOINT 'minio.example.com:9000',
    SCOPE 's3://analytics-bucket',
    URL_STYLE 'path',
    USE_SSL false
);

Connect to PostgreSQL, then choose the managed Iceberg location in the same session that creates the table:

SET pg_lake_iceberg.default_location_prefix =
    's3://analytics-bucket/warehouse';

Core Workflows

Create and modify a transactional Iceberg table:

CREATE TABLE measurements (
    station_name text NOT NULL,
    measured_at timestamptz NOT NULL,
    value double precision
) USING iceberg;

INSERT INTO measurements VALUES
    ('Istanbul', now(), 18.5),
    ('Haarlem', now(), 9.3);

Import or export Parquet, CSV, or newline-delimited JSON through COPY:

COPY (SELECT * FROM measurements)
TO 's3://analytics-bucket/export/measurements.parquet';

COPY measurements
FROM 's3://analytics-bucket/import/measurements.parquet';

Query files without loading them into PostgreSQL:

CREATE FOREIGN TABLE external_events ()
SERVER pg_lake
OPTIONS (path 's3://analytics-bucket/events/*.parquet');

SELECT count(*) FROM external_events;

Component Index

pg_lake: meta-extension and lake.version().
pg_lake_table: data-lake FDW, Iceberg table syntax, file utilities, and table catalogs.
pg_lake_iceberg: Iceberg metadata, snapshots, manifests, and catalog integration.
pg_lake_copy: COPY interception for object-store files and lake formats.
pg_lake_engine: shared query rewrite, type conversion, cleanup, and pgduck_server client layer.
pg_extension_base: preload and lifecycle-worker infrastructure.
pg_map: generated PostgreSQL map types used for nested lake data.

Operational Caveats

pgduck_server is required on every PostgreSQL host that can execute lake queries. Keep it supervised and verify its local socket before serving traffic.
The default socket mode is 0770; its owner and group come from the account that starts pgduck_server. A mismatched service user causes ERROR: could not start query engine.
S3 and compatible credentials are resolved by the DuckDB secrets/credential chain. Grant only the bucket permissions required by the workload.
The first start may download the DuckDB spatial extension. Ensure the service account has the required network access and writable state/cache directories.
CREATE PERSISTENT SECRET survives server restarts, but DuckDB stores it unencrypted under ~/.duckdb/stored_secrets. Keep the service account and its home directory stable, restrict permissions, and protect those files as credentials.
The default memory limit is 80 percent of system memory. Set --memory_limit explicitly when PostgreSQL and pgduck_server share a production host.
Iceberg writes create Parquet files per statement. Batch inserts and run regular VACUUM to avoid many small files.
The PostgreSQL extensions, pgduck_server, object-store data, and Iceberg catalog form one deployment unit. Back up and upgrade them as separate evidence layers; creating the extension alone does not prove the external services are usable.

pg_extension_base

Mon, 01 Jan 0001 00:00:00 +0000

pg_lake : Extension development kit by Snowflake

Overview

ID	Extension	Package	Version	Category	License	Language
2561	pg_extension_base	pg_lake	`3.4`	OLAP	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	No	Yes	Yes	Yes	no	no

Relationships
Schemas	`extension_base` `pg_catalog`
Need By	pg_extension_updater pg_lake_engine
See Also	pg_tle pg_readme pgextwlist ddlx pgdd meta pg_command_fw supautils
Siblings	pg_lake pg_extension_updater pg_map pg_lake_engine pg_lake_iceberg pg_lake_table pg_lake_copy

Set shared_preload_libraries=pg_extension_base. It auto-loads dependent libraries declared through the pg_lake control-file marker and manages extension lifecycle background workers. Extension SQL/control version is 3.4; source and DEB/RPM package version is 3.4.0.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`3.4`	18 17 16 15 14	`pg_lake`	-
RPM	PIGSTY	`3.4.0`	18 17 16 15 14	`pg_lake_$v`	-
DEB	PIGSTY	`3.4.0`	18 17 16 15 14	`postgresql-$v-pg-lake`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	N/A	N/A	N/A	N/A	N/A
el8.aarch64	N/A	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el9.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A

Source

Repository

github.com/Snowflake-Labs/pg_lake/tree/main/pg_extension_base

Source Tarball

pg_lake-3.4.0.tar.gz

pig build pkg pg_lake;		# 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_lake;		# install via package name, for the active PG version
pig install pg_extension_base;		# install by extension name, for the current active PG version

pig install pg_extension_base -v 18;   # install for PG 18
pig install pg_extension_base -v 17;   # install for PG 17
pig install pg_extension_base -v 16;   # install for PG 16

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_extension_base';

Create this extension with:

CREATE EXTENSION pg_extension_base;

Usage

Sources:

pg_extension_base is Snowflake’s infrastructure extension for other PostgreSQL extensions. It provides control-file-driven library preloading, database-scoped lifecycle workers, dependency-aware updates, and short-lived attached workers. Application users normally install it as a dependency of pg_lake; extension developers use its C and SQL APIs directly.

Enable the Infrastructure

pg_extension_base must be preloaded before extensions can use its startup machinery:

shared_preload_libraries = 'pg_extension_base'

Restart PostgreSQL, then create it in a database that hosts dependent extensions:

CREATE EXTENSION pg_extension_base;

SELECT * FROM extension_base.list_preload_libraries();
SELECT * FROM extension_base.list_base_workers();

Extension-Developer Workflow

A dependent extension can request startup loading with a control-file directive:

requires = 'pg_extension_base'
module_pathname = '$libdir/my_extension'
#!shared_preload_libraries

To attach a database lifecycle worker, define an internal C function and register it during extension installation:

CREATE FUNCTION my_extension.main_worker(internal)
RETURNS internal
LANGUAGE C
AS 'MODULE_PATHNAME', 'my_extension_main_worker';

SELECT extension_base.register_worker(
    'my_extension_main',
    'my_extension.main_worker'
);

The base infrastructure starts the worker after server startup, CREATE EXTENSION, or creation of a database from a template, and attempts to stop it for DROP EXTENSION or DROP DATABASE.

SQL API Index

extension_base.list_preload_libraries(): reports extension/library pairs discovered for startup loading.
extension_base.register_worker(name, regproc) and deregister_worker(name): manage lifecycle-worker registrations; public execution is revoked.
extension_base.list_base_workers(): reports database, extension, PID, and restart state for base workers.
extension_base.list_database_starters(): reports per-database starter processes.
extension_base.run_attached(command, dbname): runs a command in a short-lived worker, optionally in another database, and returns command IDs and tags.

Operational Boundaries

Lifecycle worker functions run as superuser and outside a transaction. They must start their own transactions, check interrupts, and avoid trusting user-controlled SQL.
Worker termination around failed DROP operations is best effort; worker code must tolerate the extension briefly disappearing or a stop being reversed.
run_attached is for bounded work that may commit independently of the caller. It is not a detached job queue for long-running tasks.
Version 3.4 changes no user-facing SQL objects relative to 3.3; its upgrade script is intentionally empty.

pg_extension_updater

Mon, 01 Jan 0001 00:00:00 +0000

pg_lake : Automatic extension updater

Overview

ID	Extension	Package	Version	Category	License	Language
2562	pg_extension_updater	pg_lake	`3.4`	OLAP	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	No	Yes	Yes	Yes	no	no

Relationships
Schemas	`extension_updater` `pg_catalog`
Requires	pg_extension_base
See Also	pg_tle pgextwlist pg_readme ddlx pgdd meta pg_command_fw supautils
Siblings	pg_lake pg_extension_base pg_map pg_lake_engine pg_lake_iceberg pg_lake_table pg_lake_copy

Optional packaged component. It runs installed extension updates at database start through pg_extension_base; it is not part of CREATE EXTENSION pg_lake CASCADE dependency closure. Extension SQL/control version is 3.4; source and DEB/RPM package version is 3.4.0.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`3.4`	18 17 16 15 14	`pg_lake`	`pg_extension_base`
RPM	PIGSTY	`3.4.0`	18 17 16 15 14	`pg_lake_$v`	-
DEB	PIGSTY	`3.4.0`	18 17 16 15 14	`postgresql-$v-pg-lake`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	N/A	N/A	N/A	N/A	N/A
el8.aarch64	N/A	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el9.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A

Source

Repository

github.com/Snowflake-Labs/pg_lake/tree/main/pg_extension_updater

Source Tarball

pg_lake-3.4.0.tar.gz

pig build pkg pg_lake;		# 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_lake;		# install via package name, for the active PG version
pig install pg_extension_updater;		# install by extension name, for the current active PG version

pig install pg_extension_updater -v 18;   # install for PG 18
pig install pg_extension_updater -v 17;   # install for PG 17
pig install pg_extension_updater -v 16;   # install for PG 16

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_extension_base';

Create this extension with:

CREATE EXTENSION pg_extension_updater CASCADE; -- requires pg_extension_base

Usage

Sources:

pg_extension_updater runs ALTER EXTENSION ... UPDATE for each extension whose installed version differs from its available default version when the database lifecycle worker starts. It is intended to reduce SQL/binary version mismatches after new extension files are deployed; it does not install missing extensions or replace release testing.

Enable Automatic Updates

The updater depends on pg_extension_base, which must be preloaded cluster-wide:

shared_preload_libraries = 'pg_extension_base'

After restarting PostgreSQL, create the updater in every database where automatic updates are desired:

CREATE EXTENSION pg_extension_updater CASCADE;

Creating it in template1 causes new databases cloned from that template to contain the updater. The worker does not update extensions inside the template database itself, but starts in a newly cloned database.

Runtime Behavior

The #!shared_preload_libraries directive in the updater’s control file lets pg_extension_base load its library.
Installation registers the internal extension_updater.main(internal) lifecycle worker.
At worker startup, it reads pg_available_extensions and updates entries whose installed_version differs from default_version.
A failed ALTER EXTENSION is logged as a warning and is attempted only once during that worker run.
pg_extension_updater.enable is a postmaster setting, defaults to on, and disables the worker’s updates when set to off; changing it requires a restart.

Caveats

Automatic migration can execute arbitrary upgrade SQL supplied by every installed extension. Validate packages and upgrade paths before enabling it on production databases.
Review extension dependency changes and take application-specific backups independently; a warning does not roll back unrelated successful extension updates.
There is no user-facing force-update function or per-extension allowlist in version 3.4.
Version 3.4 changes no updater SQL API relative to 3.3.

pg_map

Mon, 01 Jan 0001 00:00:00 +0000

pg_lake : Map type for PostgreSQL, bundled as a required pg_lake component.

Overview

ID	Extension	Package	Version	Category	License	Language
2563	pg_map	pg_lake	`3.4`	OLAP	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d--	No	Yes	No	Yes	no	no

Relationships
Schemas	`map_type` `pg_catalog`
Need By	pg_lake_engine
See Also	hstore pgbson collection pgjq jsquery intarray arraymath pg_jsonschema jsonschema pg_projection
Siblings	pg_lake pg_extension_base pg_extension_updater pg_lake_engine pg_lake_iceberg pg_lake_table pg_lake_copy

This packaged provider is Snowflake pg_lake pg_map 3.4, not the unrelated semenikhind/pg_map 1.0 array-mapping extension. The catalog name is unique, so the packaged provider supersedes that source-only row and is reassigned with the pg_lake family to OLAP ID 2563. Extension SQL/control version is 3.4; source and DEB/RPM package version is 3.4.0.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`3.4`	18 17 16 15 14	`pg_lake`	-
RPM	PIGSTY	`3.4.0`	18 17 16 15 14	`pg_lake_$v`	-
DEB	PIGSTY	`3.4.0`	18 17 16 15 14	`postgresql-$v-pg-lake`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	N/A	N/A	N/A	N/A	N/A
el8.aarch64	N/A	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el9.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A

Source

Repository

github.com/Snowflake-Labs/pg_lake/tree/main/pg_map

Source Tarball

pg_lake-3.4.0.tar.gz

pig build pkg pg_lake;		# 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_lake;		# install via package name, for the active PG version
pig install pg_map;		# install by extension name, for the current active PG version

pig install pg_map -v 18;   # install for PG 18
pig install pg_map -v 17;   # install for PG 17
pig install pg_map -v 16;   # install for PG 16

Create this extension with:

CREATE EXTENSION pg_map;

Usage

Sources:

pg_map generates strongly typed key/value map domains from PostgreSQL types. A generated map is an array of composite key/value pairs, with type-specific extraction, cardinality, entry, and operator functions. It is used by pg_lake for nested data but can also be used directly.

Create and Use a Map Type

CREATE EXTENSION pg_map;

-- Requires a privileged role; PUBLIC execution is revoked.
SELECT map_type.create('text', 'integer');
-- map_type.key_text_val_int

Construct a value and read it through generated functions or the -> operator:

SELECT map_type.extract(
    '{"(me,1)","(myself,2)","(i,3)"}'::map_type.key_text_val_int,
    'i'
);
-- 3

SELECT
    '{"(me,1)","(myself,2)","(i,3)"}'::map_type.key_text_val_int
    -> 'myself';
-- 2

SELECT key, value
FROM map_type.entries(
    '{"(me,1)","(myself,2)","(i,3)"}'::map_type.key_text_val_int
);

Generated API

map_type.create(keytype regtype, valtype regtype, typname text default null): idempotently creates or returns a map type for a key/value pair.
map_type.extract(map, key) and generated map -> key: return the value for a key.
map_type.cardinality(map): returns the number of entries.
map_type.entries(map): expands a map to key, value rows.
Generated names normally follow map_type.key_<keytype>_val_<valuetype>; supply typname when a controlled name is required.

Type and Lifecycle Caveats

Array types cannot be used as map keys. Array values and nested generated map types are supported.
A call to map_type.create creates PostgreSQL types, functions, and operators. Treat it as schema DDL and run it in migrations rather than per-request code.
Generated objects are registered as dependencies of pg_map; dropping the extension can remove them and columns that depend on them when CASCADE is used.
Map values use PostgreSQL composite-array syntax. Duplicate-key and ordering semantics should be tested for the application’s chosen construction path rather than assumed from JSON objects.
Version 3.4 changes no map SQL API relative to 3.3.

pg_lake_engine

Mon, 01 Jan 0001 00:00:00 +0000

pg_lake : Query engine for data lake queries

Overview

ID	Extension	Package	Version	Category	License	Language
2564	pg_lake_engine	pg_lake	`3.4`	OLAP	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	No	Yes	Yes	Yes	no	no

Relationships
Schemas	`__lake__internal__nsp__` `lake_engine` `lake_struct` `pg_catalog`
Requires	pg_extension_base pg_map
Need By	pg_lake_copy pg_lake_iceberg pg_lake_table
See Also	pg_duckdb pg_ducklake pg_mooncake duckdb_fdw pg_parquet pg_clickhouse columnar storage_engine orioledb
Siblings	pg_lake pg_extension_base pg_extension_updater pg_map pg_lake_iceberg pg_lake_table pg_lake_copy

Query-engine component. pg_extension_base auto-loads its module; delegated DuckDB execution additionally requires the separately running PG-major pgduck_server. Extension SQL/control version is 3.4; source and DEB/RPM package version is 3.4.0.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`3.4`	18 17 16 15 14	`pg_lake`	`pg_extension_base`, `pg_map`
RPM	PIGSTY	`3.4.0`	18 17 16 15 14	`pg_lake_$v`	-
DEB	PIGSTY	`3.4.0`	18 17 16 15 14	`postgresql-$v-pg-lake`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	N/A	N/A	N/A	N/A	N/A
el8.aarch64	N/A	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el9.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A

Source

Repository

github.com/Snowflake-Labs/pg_lake/tree/main/pg_lake_engine

Source Tarball

pg_lake-3.4.0.tar.gz

pig build pkg pg_lake;		# 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_lake;		# install via package name, for the active PG version
pig install pg_lake_engine;		# install by extension name, for the current active PG version

pig install pg_lake_engine -v 18;   # install for PG 18
pig install pg_lake_engine -v 17;   # install for PG 17
pig install pg_lake_engine -v 16;   # install for PG 16

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_extension_base';

Create this extension with:

CREATE EXTENSION pg_lake_engine CASCADE; -- requires pg_extension_base, pg_map

Usage

Sources:

pg_lake_engine is the shared execution layer used by the pg_lake table, copy, and Iceberg extensions. It rewrites eligible PostgreSQL work for pgduck_server, maps PostgreSQL and DuckDB values, and tracks remote files that must be removed after aborts or table changes. It is an internal dependency rather than a standalone analytics interface.

Deployment Boundary

Install it through the top-level extension so its dependency graph and preload directives remain aligned:

shared_preload_libraries = 'pg_extension_base'

CREATE EXTENSION pg_lake CASCADE;

pg_lake_engine requires pg_extension_base and pg_map. Query execution also requires a running local pgduck_server; creating only this extension does not provide a usable lake table.

User-Visible Objects

Roles lake_read, lake_write, and lake_read_write: shared privilege groups consumed by the other components.
to_postgres(any): returns its input while forcing that expression to be evaluated in PostgreSQL instead of pushed to the lake engine.
to_date(double precision): converts a days-since-Unix-epoch value commonly found in Parquet to a PostgreSQL date.
lake_engine.deletion_queue: tracks committed orphan-file cleanup; readable by lake_write.
lake_engine.in_progress_files: tracks files produced by transactions that have not committed.
lake_engine.flush_deletion_queue(regclass) and flush_in_progress_queue(): privileged cleanup functions used by maintenance paths.

SELECT to_postgres(application_only_function(payload))
FROM external_events;

Use to_postgres() only when an expression cannot or should not be pushed down; pulling data back into PostgreSQL may substantially increase transfer and execution cost.

Internal State and Caveats

The __lake__internal__nsp__ functions are planner/deparser placeholders and are not a supported direct SQL API.
Do not manually update or delete queue rows. Cleanup functions need the extension’s object-store credentials and privilege roles and should be invoked only as documented by operational tooling.
Version 3.4 adds resolve_metadata to the deletion queue so Iceberg metadata can be expanded into exact referenced files during VACUUM, moving object-store traversal off the DROP path.
Roles are cluster-wide objects and can outlive an extension instance in one database; review memberships separately when removing pg_lake.

pg_lake_iceberg

Mon, 01 Jan 0001 00:00:00 +0000

pg_lake : Iceberg implementation in Postgres

Overview

ID	Extension	Package	Version	Category	License	Language
2565	pg_lake_iceberg	pg_lake	`3.4`	OLAP	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--s-d--	No	Yes	No	Yes	no	no

Relationships
Schemas	`lake_iceberg` `pg_catalog`
Requires	pg_lake_engine plpgsql
Need By	pg_lake_copy pg_lake_table
See Also	pg_ducklake pg_parquet pg_duckdb aws_s3 file_fdw pg_bulkload duckdb_fdw pg_mooncake pg_fact_loader pg_clickhouse
Siblings	pg_lake pg_extension_base pg_extension_updater pg_map pg_lake_engine pg_lake_table pg_lake_copy

The control file declares pg_lake_engine; canonical metadata also retains plpgsql because the install SQL uses PL/pgSQL. plpgsql is installed by default in normal PostgreSQL databases. Extension SQL/control version is 3.4; source and DEB/RPM package version is 3.4.0.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`3.4`	18 17 16 15 14	`pg_lake`	`pg_lake_engine`, `plpgsql`
RPM	PIGSTY	`3.4.0`	18 17 16 15 14	`pg_lake_$v`	-
DEB	PIGSTY	`3.4.0`	18 17 16 15 14	`postgresql-$v-pg-lake`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	N/A	N/A	N/A	N/A	N/A
el8.aarch64	N/A	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el9.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A

Source

Repository

github.com/Snowflake-Labs/pg_lake/tree/main/pg_lake_iceberg

Source Tarball

pg_lake-3.4.0.tar.gz

pig build pkg pg_lake;		# 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_lake;		# install via package name, for the active PG version
pig install pg_lake_iceberg;		# install by extension name, for the current active PG version

pig install pg_lake_iceberg -v 18;   # install for PG 18
pig install pg_lake_iceberg -v 17;   # install for PG 17
pig install pg_lake_iceberg -v 16;   # install for PG 16

Create this extension with:

CREATE EXTENSION pg_lake_iceberg CASCADE; -- requires pg_lake_engine, plpgsql

Usage

Sources:

pg_lake_iceberg implements Iceberg metadata, snapshots, manifests, partition specifications, and catalog integration inside PostgreSQL. The familiar CREATE TABLE ... USING iceberg syntax is exposed by the dependent pg_lake_table component; users normally install both through pg_lake.

Create and Inspect an Iceberg Table

CREATE EXTENSION pg_lake CASCADE;

SET pg_lake_iceberg.default_location_prefix =
    's3://analytics-bucket/warehouse';

CREATE TABLE events (
    event_time timestamptz NOT NULL,
    user_id bigint NOT NULL,
    payload jsonb
) USING iceberg
WITH (partition_by = 'day(event_time), bucket(32, user_id)');

SELECT table_namespace, table_name, metadata_location
FROM iceberg_tables
WHERE table_name = 'events';

Inspect an Iceberg metadata file and its referenced state:

SELECT lake_iceberg.metadata(metadata_location)
FROM iceberg_tables
WHERE table_name = 'events';

SELECT f.*
FROM iceberg_tables AS t
CROSS JOIN LATERAL lake_iceberg.files(t.metadata_location) AS f
WHERE t.table_name = 'events';

Metadata and Catalog API

iceberg_tables: pg_catalog view combining local managed tables and external catalog entries.
iceberg_namespace_properties: catalog namespace properties.
lake_iceberg.metadata(uri): raw Iceberg metadata JSON.
lake_iceberg.files(uri): manifest path, content kind, data-file path/format, spec ID, record count, and file size.
lake_iceberg.snapshots(uri): sequence number, snapshot ID, timestamp, and manifest-list path.
lake_iceberg.data_file_stats(uri): per-file sequence and lower/upper bounds; execution is granted to lake_read rather than PUBLIC.
iceberg_catalog: version 3.4 FDW for named PostgreSQL, object-store, or REST catalog configurations.

Define a user-managed REST catalog server and keep credentials in a user mapping:

CREATE SERVER my_polaris TYPE 'rest'
FOREIGN DATA WRAPPER iceberg_catalog
OPTIONS (rest_endpoint 'https://polaris.example.com');

CREATE USER MAPPING FOR app_role SERVER my_polaris
OPTIONS (client_id 'app', client_secret 'secret');

CREATE TABLE catalog_events (id bigint)
USING iceberg
WITH (catalog = 'my_polaris');

Catalog and Storage Caveats

User-created catalog servers require their own USER MAPPING credentials and do not fall back to the built-in REST catalog credential GUCs.
The built-in postgres, object_store, and rest catalogs map to immutable extension-owned servers. Configure them through the documented GUCs rather than altering those servers.
External modifications to iceberg_tables are blocked by default because changing metadata behind pg_lake can break transaction and query-engine consistency.
Iceberg writes should be batched. Each statement can add Parquet files and snapshots; regular VACUUM compacts small files and expires data according to table/GUC policy.
Iceberg has narrower representations for some PostgreSQL values. The default out_of_range_values = 'error' preserves integrity; clamp silently changes out-of-range temporal values and replaces some unsupported values with NULL.

pg_lake_table

Mon, 01 Jan 0001 00:00:00 +0000

pg_lake : Data lake tables and Iceberg tables

Overview

ID	Extension	Package	Version	Category	License	Language
2566	pg_lake_table	pg_lake	`3.4`	OLAP	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	No	Yes	Yes	Yes	no	no

Relationships
Schemas	`__pg_lake_table_writes` `lake_file` `lake_file_cache` `lake_table` `pg_catalog`
Requires	btree_gist pg_lake_engine pg_lake_iceberg
Need By	pg_lake pg_lake_copy
See Also	pg_ducklake pg_mooncake columnar pg_parquet storage_engine orioledb pg_sorted_heap aws_s3 pg_bulkload file_fdw
Siblings	pg_lake pg_extension_base pg_extension_updater pg_map pg_lake_engine pg_lake_iceberg pg_lake_copy

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.

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`3.4`	18 17 16 15 14	`pg_lake`	`btree_gist`, `pg_lake_engine`, `pg_lake_iceberg`
RPM	PIGSTY	`3.4.0`	18 17 16 15 14	`pg_lake_$v`	-
DEB	PIGSTY	`3.4.0`	18 17 16 15 14	`postgresql-$v-pg-lake`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	N/A	N/A	N/A	N/A	N/A
el8.aarch64	N/A	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el9.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A

Source

Repository

github.com/Snowflake-Labs/pg_lake/tree/main/pg_lake_table

Source Tarball

pg_lake-3.4.0.tar.gz

pig build pkg pg_lake;		# 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_lake;		# install via package name, for the active PG version
pig install pg_lake_table;		# install by extension name, for the current active PG version

pig install pg_lake_table -v 18;   # install for PG 18
pig install pg_lake_table -v 17;   # install for PG 17
pig install pg_lake_table -v 16;   # install for PG 16

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_extension_base';

Create this extension with:

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

Usage

Sources:

pg_lake_table exposes object-store files as PostgreSQL foreign tables and provides the USING iceberg table syntax. It owns the pg_lake and pg_lake_iceberg foreign servers, file inspection/cache utilities, table catalogs, and transaction hooks; Iceberg metadata encoding is delegated to pg_lake_iceberg.

Query External Files

Install the complete stack, including the required pg_lake_engine, pg_lake_iceberg, and btree_gist dependencies:

CREATE EXTENSION pg_lake CASCADE;

An empty column list asks pg_lake to infer the file schema:

CREATE FOREIGN TABLE external_events ()
SERVER pg_lake
OPTIONS (
    path 's3://analytics-bucket/events/*.parquet',
    filename 'true'
);

SELECT count(*) FROM external_events;

Create a writable Iceberg table through the extension-provided table access method:

CREATE TABLE managed_events (
    event_time timestamptz,
    payload jsonb
) USING iceberg;

File and Table Utility Index

lake_file.list(pattern): lists matching object paths, sizes, modification times, and ETags.
lake_file.size(path) and lake_file.exists(path): inspect one remote object.
lake_file.preview(url, format, compression): returns inferred column names and types.
lake_file.delete(url): deletes a remote object; restrict it to roles that are allowed to remove data.
lake_file_cache.add(path, refresh), remove(path), and list(): manage the local file cache for members of lake_read.
lake_iceberg.table_size(regclass): totals the current data-file sizes of an Iceberg table.
Foreign servers pg_lake and pg_lake_iceberg: read-file and writable-Iceberg entry points.
Access methods iceberg and pg_lake_iceberg: aliases used to translate CREATE TABLE ... USING into the extension’s foreign-table representation.

SELECT path, file_size
FROM lake_file.list('s3://analytics-bucket/events/**/*.parquet');

SELECT *
FROM lake_file.preview('s3://analytics-bucket/events/sample.parquet');

Operational Caveats

pg_extension_base must be preloaded and pgduck_server must be running with credentials for every referenced location.
lake_read, lake_write, and lake_read_write control access to servers, schemas, and utilities. Grant the narrowest role required by each application.
External tables are references to files, not imported copies. File replacement, cross-region access, and cache invalidation can change latency or results independently of PostgreSQL catalog state.
Iceberg inserts are optimized for batches rather than single rows. Use a staging heap table for high-rate row-at-a-time ingestion and periodically flush batches.
Internal lake_table.* catalogs track files, field IDs, partitions, and recovery state. Do not modify them directly.

pg_lake_copy

Mon, 01 Jan 0001 00:00:00 +0000

pg_lake : Copy to/from data lake files

Overview

ID	Extension	Package	Version	Category	License	Language
2567	pg_lake_copy	pg_lake	`3.4`	OLAP	Apache-2.0	C

Attribute	Has Binary	Has Library	Need Load	Has DDL	Relocatable	Trusted
--sLd--	No	Yes	Yes	Yes	no	no

Relationships
Schemas	`pg_catalog`
Requires	pg_lake_engine pg_lake_iceberg pg_lake_table
Need By	pg_lake
See Also	pg_parquet aws_s3 pg_bulkload file_fdw pg_ducklake pg_fact_loader pg_csv omni_csv duckdb_fdw pg_duckdb
Siblings	pg_lake pg_extension_base pg_extension_updater pg_map pg_lake_engine pg_lake_iceberg pg_lake_table

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

Packages

Type	Repo	Version	PG Major Compatibility	Package Pattern	Dependencies
EXT	PIGSTY	`3.4`	18 17 16 15 14	`pg_lake`	`pg_lake_engine`, `pg_lake_iceberg`, `pg_lake_table`
RPM	PIGSTY	`3.4.0`	18 17 16 15 14	`pg_lake_$v`	-
DEB	PIGSTY	`3.4.0`	18 17 16 15 14	`postgresql-$v-pg-lake`	-

Linux / PG	PG18	PG17	PG16	PG15	PG14
el8.x86_64	N/A	N/A	N/A	N/A	N/A
el8.aarch64	N/A	N/A	N/A	N/A	N/A
el9.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el9.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
el10.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d12.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
d13.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u22.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u24.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.x86_64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A
u26.aarch64	PIGSTY 3.4.0	PIGSTY 3.4.0	PIGSTY 3.4.0	N/A	N/A

Source

Repository

github.com/Snowflake-Labs/pg_lake/tree/main/pg_lake_copy

Source Tarball

pg_lake-3.4.0.tar.gz

pig build pkg pg_lake;		# 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_lake;		# install via package name, for the active PG version
pig install pg_lake_copy;		# install by extension name, for the current active PG version

pig install pg_lake_copy -v 18;   # install for PG 18
pig install pg_lake_copy -v 17;   # install for PG 17
pig install pg_lake_copy -v 16;   # install for PG 16

Config this extension to shared_preload_libraries:

shared_preload_libraries = 'pg_extension_base';

Create this extension with:

CREATE EXTENSION pg_lake_copy CASCADE; -- requires pg_lake_engine, pg_lake_iceberg, pg_lake_table

Usage

Sources:

pg_lake_copy extends PostgreSQL COPY so queries, heap tables, external lake tables, and Iceberg tables can exchange Parquet, CSV, or newline-delimited JSON files with local paths, HTTP endpoints, and configured object stores. It adds behavior through hooks and has no standalone SQL function API.

Enable the Component

The normal entry point installs pg_lake_copy and its exact dependencies together:

CREATE EXTENSION pg_lake CASCADE;

Its control file requires pg_lake_engine, pg_lake_iceberg, and pg_lake_table. The deployment also needs pg_extension_base in shared_preload_libraries and a running pgduck_server.

Export and Import

Format is inferred from the path suffix or selected explicitly:

COPY (
    SELECT event_id, event_time, payload
    FROM events
    WHERE event_time >= DATE '2026-07-01'
)
TO 's3://analytics-bucket/events/july.parquet'
WITH (format 'parquet');

COPY events_archive
FROM 's3://analytics-bucket/events/july.parquet'
WITH (format 'parquet');

CSV and compressed output use standard-looking COPY options extended for the lake writer:

COPY (SELECT * FROM daily_summary)
TO 's3://analytics-bucket/summary/daily.csv.gz'
WITH (format 'csv', header true, compression 'gzip');

The destination can be a PostgreSQL heap table or an Iceberg table; the source can likewise be any query supported by the installed pg_lake stack.

Format and Runtime Boundaries

Parquet is columnar and preserves supported typed values; CSV and newline-delimited JSON have format-specific inference and conversion options documented upstream.
Object-store access runs through pgduck_server. Its credential chain, network access, and bucket permissions must permit the requested read or write.
COPY is one statement and participates in the surrounding PostgreSQL transaction, but remote files and cleanup also depend on the pg_lake transaction/queue machinery. Inspect failed operations and orphan cleanup before retrying large exports.
Version 3.4 adds no user-visible SQL objects in pg_lake_copy; its 3.3 to 3.4 upgrade script is empty.

PGEXT.CLOUD – Apache-2.0

h3

Overview

Packages

Source

Install

Usage

Base Type

Indexing Functions

Index Inspection Functions

Grid Traversal Functions

Hierarchical Grid Functions

Region Functions

Unidirectional Edge Functions

Vertex Functions

Miscellaneous Functions

Operators

SP-GiST Index (Experimental)

Type Casts

PostGIS Integration

Raster Processing

h3_postgis

Overview

Packages

Source

Install

Usage

Key Functions

qdgc

Overview

Packages

Source

Install

Usage

Core Workflow

Bounding Boxes and Level Metrics

Important Objects

Operational Notes

qdgc_postgis

Overview

Packages

Source

Install

Usage

Core Workflow

Fill an Area of Interest

Important Objects

Operational Notes

pg_tiktoken

Overview

Packages

Source

Install

Usage

Functions

tiktoken_count

tiktoken_encode

Supported Models

pg_tiktoken_c

Overview

Packages

Source

Install

Usage

Create the Extension

Encode and Count

Chunk Text

Function Index

Operational Notes

pgmnemo

Overview

Packages

Source

Install

Usage

Install

Ingest a Lesson

Recall with Confidence Filtering

Record Outcomes

Typed Memory and Navigation