Date: Wed, 16 Feb 2022 15:09:38 +0900 (JST)
Message-Id: <20220216.150938.760580034521958485.horikyota.ntt@gmail.com>
To: sawada.mshk@gmail.com
Cc: andres@anarazel.de, hlinnaka@iki.fi, pgsql-hackers@postgresql.org
Subject: Re: Race conditions in 019_replslot_limit.pl
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
In-Reply-To: <CAD21AoCmphWmVNWHa3uPDF=12z3z8yqQnBMpfSGVb+kGkvux2A@mail.gmail.com>
References: <20220215235157.jknqi73c5scietxe@alap3.anarazel.de>
	<20220216.142637.1918987197255698649.horikyota.ntt@gmail.com>
	<CAD21AoCmphWmVNWHa3uPDF=12z3z8yqQnBMpfSGVb+kGkvux2A@mail.gmail.com>
User-Agent: Mew version 6.8 on Emacs 26.1
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/20220216.150938.760580034521958485.horikyota.ntt%40gmail.com>
Precedence: bulk

At Wed, 16 Feb 2022 14:58:23 +0900, Masahiko Sawada <sawada.mshk@gmail.com> wrote in 
> On Wed, Feb 16, 2022 at 2:26 PM Kyotaro Horiguchi
> <horikyota.ntt@gmail.com> wrote:
> >
> > At Tue, 15 Feb 2022 15:51:57 -0800, Andres Freund <andres@anarazel.de> wrote in
> > > I guess it's conceivable that the backend was still working through process
> > > shutdown? But it doesn't seem too likely, given that several other connections
> > > manage to get through entire connect / disconnect cycles?
> >
> > Yes, but since postmaster seems thinking that process is gone.
> 
> Or it's possible that the process took a time to clean up the
> temporary replication slot?

Ugg, it's immediate shutdown.  So postmaster kills the walsender no
matter what state the waldender is under, nd leaves no log about the
end ofwalsender.

Sorry for the confusion.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center