[BUG] Upgrade from 2.x: compose pins postgres:15, but existing .nostr/data may be PG 16/17/18 (old unpinned postgres image)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 55/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- docker-compose, postgresql, typescript
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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
- Run nostream 2.x with the old compose (
image: postgres) — e.g. our.nostr/datahasPG_VERSION=17(image was 17.5). git checkout v3.4.1 && docker compose up -d.nostream-dbcannot start, because PostgreSQL refuses a data directory initialized by a newer major ("database files are incompatible with server"), andnostream-migrate/nostreamwait on its healthcheck. (We caught this before starting:.nostr/data/PG_VERSIONsaid 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_VERSIONand override the image to that major (same Debian variant) beforedocker compose up; - optionally, the CLI start command could read
PG_VERSIONand refuse to start with a clear message when it does not match the configured image major.
- 主要語言
- TypeScript
- 星號
- 829
- 分支
- 234
- 平均合併
- 16 小時 13 分鐘
- 30 天內合併 PR
- 74
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
cameri/nostream 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 83/100
維護者通常 1 天內回覆
-
Website
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 55/100
維護者通常 1 天內回覆
-
[BUG] LNbits >= 1.0: ISO 8601 time/expiry parsed as unix seconds, paid admissions never confirmed未關閉
難度 2/5 1-3 小時 新手友好度 25/100
維護者通常 1 天內回覆
-
feat(payments): let clients see their subscription tier可能已有人在做 @Priyanshubhartistm 於 1 天前認領。 未關閉enhancement
cameri/nostream#925 · 已指派 1 人 ·
維護者通常 1 天內回覆
相似的 Issue
-
数据界面的横向滚动条缺失未關閉
難度 2/5 1-3 小時 新手友好度 62/100
zilliztech/attu#1037 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
難度 2/5 1-3 小時 新手友好度 76/100
openclaw/openclaw#181212 · 1 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
apify/apify-mcp-server#1684 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
Automattic/data-liberation-agent#953 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
siteboon/claudecodeui#1642 ·
維護者通常 5 天內回覆