From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: Amul Sul <sulamul@gmail.com>, Andres Freund <andres@anarazel.de>,
        Andrew Dunstan <andrew@dunslane.net>,
        "Bossart,
    Nathan" <bossartn@amazon.com>,
        Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
        "masao.fujii@oss.nttdata.com" <masao.fujii@oss.nttdata.com>,
        "pgsql-hackers@lists.postgresql.org"
 <pgsql-hackers@lists.postgresql.org>,
        "mengjuan.cmj@alibaba-inc.com" <mengjuan.cmj@alibaba-inc.com>,
        "Jakub.Wartak@tomtom.com" <Jakub.Wartak@tomtom.com>,
        Ryo Matsumura <matsumura.ryo@fujitsu.com>
Subject: Re: prevent immature WAL streaming
In-reply-to: <202111251832.22chedo6btui@alvherre.pgsql>
References: <202111251832.22chedo6btui@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Thu, 25 Nov 2021 15:32:31 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <311158.1637866330.1@sss.pgh.pa.us>
Date: Thu, 25 Nov 2021 13:52:10 -0500
Message-ID: <311159.1637866330@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/311159.1637866330%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Oh, but also I think I should push a mitigation in case a production
> system hits this problem: maybe reduce the message from FATAL to WARNING
> if the registered LSN is at a page boundary.

Uh, why?  The fix should remove the problem, and if it doesn't, we're
still looking at inconsistent WAL aren't we?

			regards, tom lane