Re: sync_standbys_defined and pg_stat_replication

2025-10-18 Thread Ants Aasma
On Tue, 7 Oct 2025 at 08:59, Jeremy Schneider wrote: > For failover to work correctly, if someone changes the GUC > synchronous_standby_names to enable sync replication, then we need to > understand the exact moment when backends will begin to block in order > to correctly determine when we can fa

Re: sync_standbys_defined and pg_stat_replication

2025-10-18 Thread Jeremy Schneider
On Mon, 6 Oct 2025 22:59:33 -0700 Jeremy Schneider wrote: > For failover to work correctly, if someone changes the GUC > synchronous_standby_names to enable sync replication, then we need to > understand the exact moment when backends will begin to block in order > to correctly determine when we

sync_standbys_defined and pg_stat_replication

2025-10-17 Thread Jeremy Schneider
For failover to work correctly, if someone changes the GUC synchronous_standby_names to enable sync replication, then we need to understand the exact moment when backends will begin to block in order to correctly determine when we can failover without data loss. There's an older mailing list threa

Re: sync_standbys_defined and pg_stat_replication

2025-10-17 Thread Jeremy Schneider
On Wed, 8 Oct 2025 20:38:53 +0300 Ants Aasma wrote: > > For the other problem, my thinking is to provide a new function that > allows a user to check if synchronous replication is active. > > Ideally this function would give other information also needed by > cluster managers. Specifically when