From: SPSingh09 (@SPSingh09) <noreply+SPSingh09@github.com>
To: patroni/patroni <noreply+patroni-patroni@github.com>
Subject: [patroni/patroni] PR #3807: 3548: Fix duplicate application names for standby-cluster replication connections
Date: Wed, 18 Nov 2026 20:25:19 +0000
Message-ID: <gh-patroni-patroni-3807@github.com> (raw)
Fixes #3548. this defect is still present in v4.1.5
When a standby cluster connects to a primary cluster, replication connections currently use the standby leader’s member name as [application_name](vscode-file://vscode-app/Users/suryapratapsingh/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html). This can collide with the name of an existing member in the primary cluster.
This change assigns standby-cluster connections a unique 63-character [application_name](vscode-file://vscode-app/Users/suryapratapsingh/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html):
Prefix: geo_
Remaining 59 characters: SHA-256 digest of the local member name
Regular member connections continue using the local member name unchanged.
Tests
Added unit coverage verifying:
Local members retain their existing [application_name](vscode-file://vscode-app/Users/suryapratapsingh/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html)
Remote members receive a distinct, deterministic geo_-prefixed name
Remote [application_name](vscode-file://vscode-app/Users/suryapratapsingh/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/workbench.html) values remain 63 characters
Checklist
- [x] Added unit tests
- [x] Targeted tests pass
- [x] Existing local-member behavior remains unchanged