Message-ID: <2df227fddc659d1da61a59a54ffa11c03461a84e.camel@j-davis.com>
Subject: Re: Disallow quorum uncommitted (with synchronous standbys) txns in
 logical replication subscribers
From: Jeff Davis <pgsql@j-davis.com>
To: SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>, Bharath Rupireddy
	 <bharath.rupireddyforpostgres@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: Thu, 06 Jan 2022 23:24:40 -0800
In-Reply-To: <CAHg+QDc-3bPT52yqB-_J-_8bc6DzpxVVzvQMA99XV_0tqOR9wg@mail.gmail.com>
References: 
	<CALj2ACX-xO-ZenQt1MWazj0Z3ziSXBMr24N_X2c0dYysPQghrw@mail.gmail.com>
	 <CAHg+QDc-3bPT52yqB-_J-_8bc6DzpxVVzvQMA99XV_0tqOR9wg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/2df227fddc659d1da61a59a54ffa11c03461a84e.camel%40j-davis.com>
Precedence: bulk

On Wed, 2022-01-05 at 23:59 -0800, SATYANARAYANA NARLAPURAM wrote:
> I would like to propose a GUC send_Wal_after_quorum_committed which
> when set to ON, walsenders corresponds to async standbys and logical
> replication workers wait until the LSN is quorum committed on the
> primary before sending it to the standby. This not only simplifies
> the post failover steps but avoids unnecessary downtime for the async
> replicas. Thoughts?

Do we need a GUC? Or should we just always require that sync rep is
satisfied before sending to async replicas?

It feels like the sync quorum should always be ahead of the async
replicas. Unless I'm missing a use case, or there is some kind of
performance gotcha.

Regards,
	Jeff Davis