Geo: Secondary site shows as unhealthy with logical replication
## Issue When using PostgreSQL logical replication for Geo, the secondary site incorrectly shows as unhealthy in the Admin UI, even though replication is working correctly. ## Symptoms - Secondary site appears unhealthy in Admin UI ![Screenshot_2026-02-19_at_13.56.02](/uploads/c29861c7b17e9186443d0e63aefec720/Screenshot_2026-02-19_at_13.56.02.png){width=836 height=600} - `gitlab-rake gitlab:geo:check` reports: ``` Database replication enabled? ... no Try fixing it: Follow Geo setup instructions to configure primary and secondary nodes for replication For more information see: https://eu-west2.nwestbury-envs.com/help/administration/geo/setup/database.md Database replication working? ... no ``` ## Root Cause The health check is not recognizing PostgreSQL logical replication as a valid replication method. It appears to only check for streaming replication. ## Investigation - Attempted to enable feature flag `geo_postgresql_replication_agnostic` but no change - Data is actually replicating correctly despite the health check failures ## Expected Behaviour The health check should recognize logical replication as a valid replication method and report the secondary site as healthy when logical replication is functioning correctly.
issue