docs(db): Postgres 14 to 18, the database role, restore limits and the manual rollback

- Database-Postgres: supported versions, the version 18 client and the tool
  search order, sslrootcert with a client before 16, how to create a role
  that is not a superuser and move an older compose install to one, a
  current schema other than public, and the space a restore needs.
- Updating: the manual rollback clears the whole schema and loads the copy
  in one transaction, as TREK's restore does; dropping only the tables left
  the collation, the trigger functions and the sequences behind. A unit
  test keeps the printed statement equal to CLEAR_SCHEMA_SQL, and the boot's
  rollback hint points at that section.
- Troubleshooting, Install-Docker-Compose, Environment-Variables, README
  and server/CLAUDE.md follow.
This commit is contained in:
Maurice
2026-11-17 11:58:35 +01:00
parent eab501925f
commit 633e9bcdc1
10 changed files with 164 additions and 33 deletions
@@ -216,8 +216,9 @@ export function postgresSafetyNet(
const match = snapshots.find((snapshot) => path.basename(snapshot).startsWith(`${PREFIX}${thisRelease}-`));
if (match) {
return (
`The copy taken right before the newer TREK migrated it is ${match}: stop TREK, empty the database ` +
'(drop and recreate it), and restore it with pg_restore --no-owner --no-privileges --single-transaction.'
`The copy taken right before the newer TREK migrated it is ${match}: stop TREK and load it as the wiki ` +
'page Updating describes ("Rolling back a Postgres update"), which clears the schema and runs ' +
'pg_restore --no-owner --no-privileges in one transaction with psql.'
);
}
if (snapshots.length > 0) {