Checking against doze Real local Postgres, declared not scripted.
doze/postgres$ doze add postgresThree lines in doze.hcl give you a real Postgres. Nothing starts until something connects.
module postgres "postgres" { version = 18 }
app "orders" { run = "go run ./services/orders" env = { DATABASE_URL = module.postgres.url } }
Your app sees postgres://postgres@127.0.0.1:5432/postgres?sslmode=disable. The database is named after the instance. doze env prints it for tools outside doze.hcl.
import ( "context" "os" "github.com/jackc/pgx/v5/pgxpool" ) func open(ctx context.Context) (*pgxpool.Pool, error) { // The first connection wakes Postgres; it can take a moment. return pgxpool.New(ctx, os.Getenv("DATABASE_URL")) }
import pg from "pg"; // The first connection wakes Postgres; it can take a moment. export const pool = new pg.Pool({ connectionString: process.env.DATABASE_URL });
import os import psycopg # The first connection wakes Postgres; it can take a moment. conn = psycopg.connect(os.environ["DATABASE_URL"])
$ psql "$(doze url postgres)"
Node: new pg.Pool({ connectionString: process.env.DATABASE_URL }) · Python: psycopg.connect(os.environ["DATABASE_URL"]) · psql: psql "$(doze url postgres)"
The setups people write most, each complete. Paste one over the block above.
Each service connects as itself and can touch only its own tables. The schema shares the role's name, so the default search_path finds it.
module postgres "postgres" { version = 18 role "orders" { password = "orders" } role "payments" { password = "payments" } schema "orders" { owner = "orders" } schema "payments" { owner = "payments" } }
Name the extension; doze fetches the build for your Postgres major and platform, pins it in doze.lock and runs CREATE EXTENSION.
vector: versions, platforms, how to querymodule postgres "postgres" { version = 18 extensions = ["vector"] }
18 takes the newest 18.x at first use (today 18.6) and then never moves. Quote a version with a dot: as a number, 17.10 would read as 17.1.
module postgres "postgres" { version = "18.4" }
A second instance on its own port. Reset wipes its rows; the next connection brings your roles and schemas back. Parallel workers each create and drop their own database inside it.
module postgres "test" { version = 18 port = 5433 sleep = "30s" }
$ doze reset test --yes $ doze run -- go test ./...
16 extensions by name, coming in postgres 0.3: doze fetches each for your Postgres major and platform. Contrib ones (pg_trgm, uuid-ossp, hstore, citext) ship with Postgres and work now.
vectorVector similarity search for embeddings (HNSW, IVFFlat).
pg_cronCron-style jobs run inside the database.
postgisGeographic objects, spatial indexes and functions.
timescaledbHypertables and time_bucket (Apache-only build).
pgmqLightweight message queues, like SQS, in tables.
pg_searchBM25 full-text search.
Preloads: doze adds it to shared_preload_libraries and restarts the instance once when the set changes.
doze holds port 5432. The first connection wakes Postgres and is handed over once it is ready.
With no connection open for 2m it goes to sleep; the data stays on disk. sleep = "never" keeps it on.
Roles, schemas, grants and extensions: creates what is new, changes what changed, drops what you removed.
Change 17 to 18, then doze migrate postgres: dump, fresh cluster, restore. The old data is kept beside it.
fsync off, 16MB shared_buffers, 50 connections. Set fsync = true when you need it crash-safe.
The module and the Postgres build are pinned by sha256 in doze.lock. Commit it.
Each line says where it comes from, so you can check it.
ed25519 key Nu5y8mbj…GWjw=, compiled into doze, over every file and over the whole index. How signing works
macOS arm64, Linux x86_64, Linux arm64, each with its own sha256, in every release.
signed indexEvery argument on the Reference tab converged into a running server, once per major, before a release is signed.
doze-modules CI · newBy doze 0.2 with doze lint --offline, on every change to the registry.
doze-modules/modules/postgres, Apache-2.0; Postgres builds from doze-binaries.
GitHub