Feedback-ID: i0fe9450f:Fastmail
Date: Tue, 17 Mar 2026 08:26:19 +0900
From: Michael Paquier <michael@paquier.xyz>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>,
	Andres Freund <andres@anarazel.de>,
	Alexander Lakhin <exclusion@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record
Message-ID: <abiRmwKizJsfa1_P@paquier.xyz>
References: <2631a3c3-5e60-4a1a-9e20-377024322602@gmail.com>
 <CAO6_Xqq73TPa3M6nQ7RqRhKkcphy1JX7aNGTYy-x_Sn+6a8Z_Q@mail.gmail.com>
 <CAHGQGwGvnpN=2bo+F7H90YLFcx9=SazwLkcx+0gEcrbQy5NVZg@mail.gmail.com>
 <CAHGQGwECpyJtMqkCEvyqgZDiwAeMj3RKobui7jONrDd35W0x3Q@mail.gmail.com>
 <vzguaguldbcyfbyuq76qj7hx5qdr5kmh67gqkncyb2yhsygrdt@dfhcpteqifux>
 <CAO6_Xqq=-KnxrFQvmyF++XH4ngtXVhcDB979rEn6SPtUhSmNYg@mail.gmail.com>
 <CAHGQGwGpfEsBJBLQDou7xccnb0tj1T_NQv2gZfuQfgzn_b=RsQ@mail.gmail.com>
 <CAHGQGwFsuPcC7Aov73FTqMC5LEOdZ6uoWno5BR1HX2LnZRNKBw@mail.gmail.com>
 <CAO6_XqqvqMqUgZ0swSkB2VNUFos6b6Vbt9BpOEGCHz4nCQEi+g@mail.gmail.com>
 <CAHGQGwFxoU0O6BDPp1_7D9aYh--sp9csC2WtiUkMR36oLXRCuA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="Nc1Qt+SmxRk4ZXPG"
Content-Disposition: inline
In-Reply-To: 
 <CAHGQGwFxoU0O6BDPp1_7D9aYh--sp9csC2WtiUkMR36oLXRCuA@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/abiRmwKizJsfa1_P%40paquier.xyz>
Precedence: bulk


--Nc1Qt+SmxRk4ZXPG
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 17, 2026 at 08:16:08AM +0900, Fujii Masao wrote:
> On Mon, Mar 16, 2026 at 6:45=E2=80=AFPM Anthonin Bonnefoy
> <anthonin.bonnefoy@datadoghq.com> wrote:
>> Thanks for the updated patch! I've run my test script against the
>> patch and there's no more "xlog flush request xxx is not satisfied"
>> errors reported.
>=20
> Thanks for the test! I've pushed the patch.

This stuff seems sensible enough that I think we should at least have
a test, no?  It does not have to be absolutely perfect in terms of
reproducibility, just good enough to be able to detect it across the
buildfarm.  We already do various things with page boundaries in WAL
during recovery, and a shutdown could be perhaps timed to increase the
reproducibility rate of the issues discussed?
--
Michael

--Nc1Qt+SmxRk4ZXPG
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmm4kZsACgkQnvQgOdby
QH1+xQ/+Og2gEvoAe62j5tK20yr4UIKkHm+bZ/7xpgUCbuIZ1zbzoOnscxts/7FF
3GLHLgb5HOkN8D9HuA0r2kSm+SFB8K6ilzeEBYkGbAwBbQKQT4inyIZxzHFEWtFQ
JEXNDHebEc2ejw6Ol+fFSkkb8OevTetZ0Mueblm8UihxhhRbLSy/rKhvPWWT3opJ
oCeKVFmctlvSlmECfl4qLKIApxd2vl4r7S116zaTqekOK5KyR7uYj1EGBEJf0OND
M6rDZTKkuxtx080d6c8dZxcm5e7q40OmEVUuY+A7YMSsd5gWFal22Ow9T8xWWHVC
rBXpaApO/60GnrxbDt7rbauM7b+jvUpktj8cq2d//iIBwow5hTlbLp7VUiKCSgMu
HkG5hOItwFinXlVMT0wbyGiBGAULMvkkKuNclZMxx5BB/dgkqf/JfPvo21CC1BwM
3VHsOrT6vRNVnHNfljH8Bk3Kj73zJ+0DfuMhFuD4zt50u+qh4BxuVjFydhhVjj1d
biYx3y5xostafdJivlqp5iEkQi6oZnVmn8zfYnYMIues6EHW0mGOSaqw87gBZnh5
lBq5hofJix29YQK0KtpiLG82iUbgd65BAMG+voNaBrnv9urkVjqUWm/ymvEoPdZA
AbiqxrSRnQTerd5+6F/v0XIeCVVjPNboMiU0jRGNlTQSqJNZA2g=
=aADo
-----END PGP SIGNATURE-----

--Nc1Qt+SmxRk4ZXPG--