Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[BUG] Upgrade from 2.x: compose pins postgres:15, but existing .nostr/data may be PG 16/17/18 (old unpinned postgres image)

Offen
  • Stimmt etwas nicht?
#928 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
55/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
docker-compose, postgresql, typescript
Bereich
databases, devops

Rechercherichtung

Read the release notes or upgrade documentation and the compose configuration for nostream-db; the report identifies .nostr/data/PG_VERSION as the way to check the existing cluster version. Start by confirming which PostgreSQL image major and Debian variant the upgrade instructions should use. Done means the upgrade guidance explains how operators can match the image to their existing data directory.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Describe the bug
#393 (for #387) pinned nostream-db to postgres:15. Before that the compose file used the unpinned postgres image, so existing installs created .nostr/data with whatever major version was latest at the time — 16, 17 or 18. After upgrading such an install to 3.x, postgres:15 cannot open the data directory and the relay never starts. The bind mount ${PWD}/.nostr/data is still used, so the old data is picked up — just by the wrong major version.

To Reproduce

  1. Run nostream 2.x with the old compose (image: postgres) — e.g. our .nostr/data has PG_VERSION = 17 (image was 17.5).
  2. git checkout v3.4.1 && docker compose up -d.
  3. nostream-db cannot start, because PostgreSQL refuses a data directory initialized by a newer major ("database files are incompatible with server"), and nostream-migrate/nostream wait on its healthcheck. (We caught this before starting: .nostr/data/PG_VERSION said 17 while the compose file says 15, so we did not run 15 against the data.)

Expected behavior
Upgrading from 2.x either keeps working or stops with a clear message telling the operator which image to use.

System

  • OS: Ubuntu 22.04
  • Platform: docker compose v5.4
  • Version: 2.1.0 → 3.4.1, data dir PG 17

Workaround we use
docker-compose.override.yml next to the upstream file:

services:
  nostream-db:
    image: postgres:17.10-bookworm

Note the -bookworm suffix: the old postgres image was Debian 12 based, current postgres:17 is Debian 13 with a newer glibc. Our database uses the libc collation en_US.utf8, and switching glibc versions under an existing cluster can silently invalidate text indexes — so the variant should match the one that created the data.

Suggestion

  • an upgrade note in the release notes / docs: check cat .nostr/data/PG_VERSION and override the image to that major (same Debian variant) before docker compose up;
  • optionally, the CLI start command could read PG_VERSION and refuse to start with a clear message when it does not match the configured image major.
Vorherrschende Sprache
TypeScript
Sterne
829
Forks
234
Ø Merge
16 Std. 13 Min.
Gemergte PRs (30 T.)
74

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus cameri/nostream

Alle Issues in cameri/nostream

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.