Re: SyncRepLock acquired exclusively in default configuration

Ashwin Agrawal <aagrawal@pivotal.io>

From: Ashwin Agrawal <aagrawal@pivotal.io>
To: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Andres Freund <andres@anarazel.de>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Simon Riggs <simon@2ndquadrant.com>, Xin Zhang <xzhang@pivotal.io>, Asim Praveen <apraveen@pivotal.io>
Date: 2020-05-19T15:56:13Z
Lists: pgsql-hackers
On Mon, May 18, 2020 at 7:41 PM Masahiko Sawada <
masahiko.sawada@2ndquadrant.com> wrote:

> This item is for PG14, right? If so I'd like to add this item to the
> next commit fest.
>

Sure, add it to commit fest.
Seems though it should be backpatched to relevant branches as well.

Commits

  1. Avoid unnecessary acquisition of SyncRepLock in transaction commit time.

  2. Fix race condition when changing synchronous_standby_names