Message-ID: <gh-pgjdbc-pgjdbc-3974@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 17 Mar 2026 19:01:30 +0000
Subject: [pgjdbc/pgjdbc] PR #3974: test: fix flaky LogicalReplicationStatusTest by polling pg_stat_replication
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Id: 213894
X-GitHub-Author-Login: vlsi
X-GitHub-Issue: 3974
X-GitHub-Labels: building-and-testing
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-State: merged
X-GitHub-Type: pull_request
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3974
Content-Type: text/plain; charset=utf-8

The tests were flaky because they assumed `forceUpdateStatus()` is synchronous — that `pg_stat_replication` immediately reflects the sent values. In reality `forceUpdateStatus()` only flushes data to the TCP socket; the server needs time to process the standby status update.

The fix is to add retry loop so the test picks up the new value if so.