Check against your doze
Checking against doze
PostgreSQL
OfficialSignedReal local Postgres, declared not scripted.
doze/postgres$ doze add postgres- Newest
- 0.2.4 · 2 Nov 2026
- Needs
- any doze
- Runs
- Postgres 14 – 18
- Platforms
- macOS arm64 · Linux arm64 · Linux x86_64
- Licence
- Apache-2.0
- Source
- doze-modules
Versions
Four releases resolve, newest first. Nothing is ever taken down: a project pinned to any of them keeps working, and doze modules upgrade is the only thing that moves a pin.
Any doze, every release
- postgres 0.2.1 – 0.2.4Currentany dozeJul–Nov 2026. No oldest-doze field, so they run on every doze, 0.1.0 and up.
- postgres 0.3Comingdoze 0.2.0 or newerExtensions by name. Built on a branch, not released.
The release tool writes the field from the SDK the module was built with, always as three numbers. A doze older than a release's minimum skips it and takes the newest release that fits.
doze 0.1.1 can't read a release's minimum doze. Update doze first, with brew upgrade doze, then run doze modules upgrade.
All releases
| Version | Released | Status | Needs doze | Protocol | Postgres | Platforms | Notes |
|---|---|---|---|---|---|---|---|
| 0.3 | Coming. Not in the index yet, so doze can't resolve it. | ||||||
| 0.3.0 | not released | Coming · extensions by name | doze 0.2.0 | 1 | 1415161718 | macarmx86 | extensions = ["vector", "pg_cron"], each bundle pinned in doze.lock. Preview the catalog |
| 0.2 | 4 in the index · newest 0.2.4 | ||||||
| 0.2.4 | 2 Nov 2026 | Current | any doze | 1 | 1415161718 | macarmx86 | A console: an Activity tab (sessions, their queries, Cancel or Terminate) and a databases table. |
| 0.2.3 | 3 Jul 2026 | Superseded | any doze | 1 | 1415161718 | macarmx86 | |
| 0.2.2 | 3 Jul 2026 | Superseded | any doze | 1 | 1415161718 | macarmx86 | The readiness check connects as -U postgres, not your OS user. |
| 0.2.1 | 2 Jul 2026 | Superseded | any doze | 1 | 1415161718 | macarmx86 | The first release in the signed index (protocol 1). |
No release matches these filters.
No download counts here: doze sends no telemetry, so nobody, including us, knows how often a release is fetched. Security advisories: none known for any release.
Not in the index
GitHub has older postgres builds than the registry lists. doze only resolves what the signed index names, so these can't land in a doze.lock.
- 0.1.0, 0.1.127–28 Jun 2026. Built before protocol 1 and the signed index (2 Jul).
- 0.2.02 Jul 2026. Replaced by 0.2.1 the same day, before it was listed. [why]
- All files on GitHub
Upgrading a project
A project stays on the release in its doze.lock until you move it. Check first; the upgrade takes the newest release your doze can run, verifies it, and rewrites the pin.
$ doze modules upgrade --check ENGINE SOURCE PINNED SELECTED STATUS postgres doze/postgres 0.2.3 0.2.4 upgrade available 1 module upgrade(s) available — run doze modules upgrade
$ doze modules upgrade postgres ENGINE SOURCE PINNED SELECTED STATUS postgres doze/postgres 0.2.3 0.2.4 upgraded doze.lock updated — commit it so the team and CI pick up the same builds
On doze 0.1.1, update doze first: it can't read a release's minimum doze. Engine pins (postgres "17") never move with a module upgrade.
modules:
doze/postgres:
- version: 0.2.3
+ version: 0.2.4
protocol: 1
engines:
- "14"
- "15"
- "16"
- "17"
- "18"
hashes:
- aarch64-apple-darwin: sha256:b92e4a9242e1a042cd368ad2c0328a9a04c510eb10669827edd45e22091cbb46
- aarch64-unknown-linux-gnu: sha256:0c615d46b24495a05583d4a684e68b4f802f18179c7a063ac11fdad5e7278db9
- x86_64-unknown-linux-gnu: sha256:4fad3b7e5378eff742031b36a21199a656b17b2fde263f6f479a695449ecc5e3
+ aarch64-apple-darwin: sha256:a07134d07cf988862f5b2d1a288cc43a40ace5b96e88e190b5d66ca8b207b89a
+ aarch64-unknown-linux-gnu: sha256:f29c48e5dab175d6f1b2991f274e2e5aedb55a9993eff90128feb423380fd2a2
+ x86_64-unknown-linux-gnu: sha256:7c920599a5a52f4ed4306963797e88de7ed6beb0be130b8b1039f7c7d0354f68