Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#928 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
55/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
docker-compose, postgresql, typescript
Domaine
databases, devops

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
TypeScript
Étoiles
829
Forks
234
Merge moyen
16 h 13 min
PR mergées (30 j)
74

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de cameri/nostream

Toutes les issues de cameri/nostream

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.