controlPanel/api
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(replicas): connect publisher via unix socket or postgres user

Browse Source 
TCP 127.0.0.1:15432 is often closed; dump/count now fall back to the
cluster socket and runuser -u postgres, which already works on master.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
mohmdsdg
2026-08-18 15:10:06 +03:30
co-authored by Cursor
parent 82f63d224e
commit d055c50b94
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/replicas.env.example
+3 -3
View File
@@ -10,6 +10,6 @@ postgresql://USER:PASSWORD@SLAVE_2_IP:5432/superadmin"
# Read-only app user on replicas (program-settings API). Grants re-applied after data repair.
# REPLICA_APP_DB_USER=montime
# Publisher DB. Prefer this if DATABASE_URL password contains @ (must be URL-encoded here).
# Master on montech-01 listens on 15432:
# PUBLISHER_DSN="postgresql://montime:09128081392%40Montime@127.0.0.1:15432/superadmin"
# Optional. If TCP 127.0.0.1:15432 is refused, omit this — the script falls back
# to unix socket / `runuser -u postgres` on port 15432.
# PUBLISHER_DSN="host=/var/run/postgresql port=15432 dbname=superadmin user=postgres"