Custom Supabase Postgres withpgrx
KBVE's custom Supabase-based PostgreSQL image. It builds a pgrx Rust extension plus pg_failover_slots against PostgreSQL 17 and bakes them into a Supabase-compatible container — shipping extra SQL functions (backed by the jedi library) without forking the upstream database.
jedi regex inside Postgres
The kilobase extension compiles Rust into a Postgres cdylib, exposing immutable, parallel-safe functions like pgrx_extract_email that reuse zero-copy jedi regex helpers so extraction runs directly inside the database.
- Base — Supabase Postgres (PostgreSQL 17).
- Toolchain — cargo-pgrx 0.16.1.
What it gives you
Features
Custom pgrx extension
Compiles Rust into a Postgres cdylib, exposing immutable, parallel-safe functions like pgrx_extract_email and pgrx_extract_github_username.
jedi integration
Reuses zero-copy regex helpers from the jedi library so extraction runs directly inside Postgres.
Failover slots
pg_failover_slots is built and layered in for replication slot failover.
Supabase-compatible
Extends the upstream Supabase Postgres image rather than forking it, tagged after the base version.
Questions
Frequently asked
What is Kilobase?
Kilobase is KBVE's custom Supabase-based PostgreSQL image. It builds a pgrx Rust extension plus pg_failover_slots against PostgreSQL 17 and bakes them into a Supabase-compatible Postgres container.
What does the Kilobase pgrx extension add?
The kilobase extension exposes pgrx functions such as pgrx_extract_email and pgrx_extract_github_username that reuse jedi library zero-copy regex helpers as immutable, parallel-safe SQL functions.
What Postgres version does Kilobase target?
Kilobase builds against PostgreSQL 17 (pgdg dev-17) with the pg17 feature by default, using cargo-pgrx 0.16.1, and tags its image after the underlying supabase/postgres version.