Write a PostgreSQL trigger or stored function using Ruby, PHP, or JavaScript syntax instead of plpgsql.
Move application logic into the database while keeping the generated code transparent and reviewable.
Speed up string building inside a database function loop using the project's optimized string builder.
Standardize a team's database functions on familiar syntax without loading extra language runtimes.
| commandprompt/plx | 0xblackash/cve-2026-46333 | am2r-android/am2r-autopatcher-android | |
|---|---|---|---|
| Stars | 17 | 17 | 17 |
| Language | C | C | C |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 4/5 | 4/5 | 2/5 |
| Audience | developer | researcher | general |
Figures from each repo's GitHub metadata at analysis time.
Requires building the C extension against pg_config and PostgreSQL versions 13 through 18.
This project is a PostgreSQL extension that lets you write database stored functions and triggers using the syntax of a programming language you already know, such as Ruby, PHP, JavaScript, TypeScript, Python, Go, COBOL, Oracle PL SQL, or Transact SQL, instead of learning PostgreSQL's own function language called plpgsql from scratch. Normally, putting logic directly inside the database, in things like triggers and stored functions, is good practice because it runs closest to the data, but the required plpgsql syntax feels unfamiliar to developers who spend their day in other languages. This project solves that by translating your familiar code into plpgsql automatically at the moment you create the function, rather than running a separate language interpreter inside the database at every call. The result is that your function still runs as ordinary, fast, trusted plpgsql, and you can inspect the generated plpgsql code at any time to see exactly what will execute. This differs from other approaches that let you write PostgreSQL functions in familiar languages, which typically load a whole separate language runtime into the database and often require superuser permissions because they are considered untrusted. Since this project only changes the syntax you type and not what actually executes, its performance is close to native plpgsql, and it even includes an optimized way of building strings inside loops that can be dramatically faster than the usual plpgsql approach on newer PostgreSQL versions. It works with PostgreSQL versions 13 through 18 and is installed as a standard PostgreSQL extension you compile and load into your database. It is aimed at application developers and teams who want to move logic into PostgreSQL without giving up the syntax they already know, and who want the resulting database code to stay transparent and reviewable rather than hidden inside an opaque runtime.
A PostgreSQL extension that lets you write database functions in familiar languages like Ruby or JavaScript, which get compiled into fast, transparent plpgsql.
Mainly C. The stack also includes C, PostgreSQL, plpgsql.
The README does not state a license, so usage terms are unclear without checking the repository's license file directly.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.