gopgext builds PostgreSQL extensions from plain Go code, using TinyGo. Mark a function with //gopgext:function and it becomes a SQL function: gopgext writes the C glue, the install script and the control file.

Experimentalgopgext is experimental. Don’t use it in production: a bug in the generated code or the Go runtime runs inside the server, where it can crash it or corrupt data, and the API and generated SQL may change without notice.
A project is plain Go files. The standard library works: fmt, regexp, encoding/json, crypto/*, maps, generics, iterators, defer/recover.
Strings, numbers, arrays, NULLs, sets, rows, timestamps, UUIDs and JSON map to SQL types. Define your own data types and composite types in Go.
Run SQL through SPI, return errors with SQLSTATE codes, log, read settings and stay responsive to query cancellation.
Write triggers, aggregates, GiST, GIN, SP-GiST and BRIN operator classes, index access methods, foreign data wrappers and query hooks.
Ports of PostgreSQL’s contrib modules (pgcrypto, hstore, pg_stat_statements, cube, …) pass upstream’s regression tests.
Several Go extensions load in one backend. PostgreSQL errors never unwind through Go frames, and results are copied into PostgreSQL memory.
package main
import (
"strings"
"gopgext/pg"
)
// Hello returns a greeting for name.
//
//gopgext:function immutable parallel=safe
func Hello(name string) string {
return "Hello, " + name + "!"
}
// Shout upper-cases s. An empty string raises an error.
//
//gopgext:function immutable parallel=safe
func Shout(s string) (string, error) {
if s == "" {
return "", pg.Errorf(pg.CodeInvalidParameterValue, "nothing to shout")
}
return strings.ToUpper(s) + "!", nil
}
func main() {} // runs once per backend, when PostgreSQL loads the library
gopgext init hello # creates hello/go.mod and hello/main.go
gopgext install hello # builds hello.so, hello.control, hello--1.0.sql and installs them
psql -c 'CREATE EXTENSION hello' -c "SELECT hello('world')"
# hello
# ---------------
# Hello, world!
The tutorial walks through it step by step.
gopgext uses the same approach as gokm, which builds Linux kernel modules from Go: a custom TinyGo target and runtime layer for the host, a C runtime compiled by the host’s own build system (PGXS here, kbuild there), and generated glue.