Re: Handle infinite recursion in logical replication setup - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Handle infinite recursion in logical replication setup
Date
Msg-id 202205050911.3q6wrtzn6fcv@alvherre.pgsql
Whole thread Raw
In response to Re: Handle infinite recursion in logical replication setup  (vignesh C <vignesh21@gmail.com>)
Responses Re: Handle infinite recursion in logical replication setup  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
On 2022-May-04, vignesh C wrote:

> On Mon, May 2, 2022 at 5:49 AM Peter Smith <smithpb2250@gmail.com> wrote:

> > 1. Commit message
> >
> > In another thread using the terminology "multi-master" seems to be
> > causing some problems. Maybe you should choose different wording in
> > this commit message to avoid having the same problems?
> 
> I felt, we can leave this to committer

Please don't.  See
https://postgr.es/m/20200615182235.x7lch5n6kcjq4aue@alap3.anarazel.de

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Add WAL recovery messages with log_wal_traffic GUC (was: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display)
Next
From: Bharath Rupireddy
Date:
Subject: Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?)