Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiU0r-0005nD-M7 for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Oct 2022 05:10:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oiU0p-0000wS-HW for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Oct 2022 05:10:35 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiU0n-0000vl-Tp for pgsql-hackers@lists.postgresql.org; Wed, 12 Oct 2022 05:10:35 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiU0g-0007Gg-7n for pgsql-hackers@lists.postgresql.org; Wed, 12 Oct 2022 05:10:32 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 76BAF32003F4; Wed, 12 Oct 2022 01:10:23 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 12 Oct 2022 01:10:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1665551423; x=1665637823; bh=beB8Ko0qZP NH19qKQIUs5QhbdVAWxsYQIvsqSFtCtO0=; b=F/Fd/EVdATfOPcpvIgg0fmZZP2 icYGMScydJI7fQgb/JsXZtRebumxq/CbR7QDdbAtQjnGm17MW1asf8LvQrSE0ztn 06pBaJXi402Ifj+Cd8aAJsPNQXU/8ZmUhPxkLtna6BdZUGnhREY7jkk7fXoc+JrZ aVnCMP27OSaO+AjS+m2N/5LoooLPVhAljuYSGv01shvH9sXBa8V7eYcTqQM5Qoz+ KwIFGANFTJG7jfAUkP3D2mnqM78O93gkTqRiQPoprZgnF9avapt00qiGa6fYv7p/ k0bGhRC/JgFOVI1v439Hhj69u4X9Exj6Jvk1nTj+sRENdWzfvcE56e7TBuRA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1665551423; x=1665637823; bh=beB8Ko0qZPNH19qKQIUs5QhbdVAW xsYQIvsqSFtCtO0=; b=MgM2ynzFKAdUrT6WynoC6d4VPpNWQxR+CyovI1lIhAHP R1L1QTWKoNNFhw6xsyLLlviUT7EyuenmbG4M0Z7ihY9+eB0UtB61Yociu1MikkKg GBKSFmaVcWZ9RQT2QnJLwSQ98nZaSECesQLVHdrdIxINpYkDH67nIo+LmNxKsO9t K61Wz2ON4YRDr5qZ8+tvqKqwQnYYSrf+hMY7ZJYvQiyt7ehENDCsSG/gJRDdPIxH jQALf12winX57nrajpS9/ryVarNqaPfEpLGusKpBn/MsGwCqCmRBZlcc+x8QJWTt gI14KTplPiahVx/EVw7n71p/OFNk2tpJf9p5VNDcKQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeejjedgleefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdljedtmdenucfjughrpeffhf fvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghq uhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvg hrnhepteelieefudffhffhtdetleeggeegfffhkeeuveetiefgudduvedutefggeeivdej necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhitg hhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 12 Oct 2022 01:10:20 -0400 (EDT) Date: Wed, 12 Oct 2022 14:10:15 +0900 From: Michael Paquier To: Kyotaro Horiguchi Cc: andres@anarazel.de, jchampion@timescale.com, y.sokolov@postgrespro.ru, dilipbalaut@gmail.com, rjuju123@gmail.com, pgsql-hackers@lists.postgresql.org Subject: Re: Error "initial slot snapshot too large" in create replication slot Message-ID: References: <20220912215156.zi52zu6n7od3k3v3@awork3.anarazel.de> <20220913.154507.1031550660908356731.horikyota.ntt@gmail.com> <20220913.161534.1763577367544098635.horikyota.ntt@gmail.com> <20220913.173105.1366509818461708829.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GCiYkmPM1sA5/Ovk" Content-Disposition: inline In-Reply-To: <20220913.173105.1366509818461708829.horikyota.ntt@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --GCiYkmPM1sA5/Ovk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 13, 2022 at 05:31:05PM +0900, Kyotaro Horiguchi wrote: > And ExportSnapshot repalces oversized subxip with overflowed. >=20 > So even when GetSnapshotData() returns a snapshot with oversized > subxip, it is saved as just "overflowed" on exporting. I don't think > this is the expected behavior since such (no xip and overflowed) > snapshot no longer works. >=20 > On the other hand, it seems to me that snapbuild doesn't like > takenDuringRecovery snapshots. >=20 > So snapshot needs additional flag signals that xip is oversized and > all xid are holded there. And also need to let takenDuringRecovery > suggest subxip is oversized. The discussion seems to have stopped here. As this is classified as a bug fix, I have moved this patch to next CF, waiting on author for the moment. -- Michael --GCiYkmPM1sA5/Ovk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmNGTDcACgkQnvQgOdby QH0czA//VhPRRrXFSab1mjtl9i/FBZfrH5qkuAEe6wG3b5geNY4L3+H7iiFOK+Kv qZb+GNIfGNDB3+2qkWSajxV7JnsImSBBlHI+35UbmxXAXxzJ4pWVlSeWApVwzBWb eKPAmee5oAaB11v94NAlgiKSTVLY0X9ZQSuZjPD7X7igQvw75rNzE+LAywt9fEAe NTxCLxL2RHu5vsFkEN7+DdpmJW0AjZWTAJwoBqVBebm/XD56Vscjav/hMefvKflC hf09o1dLKvB+czdruI0Ir3+PLZHbpPK7OHU71S4rOYGiBmu19Yi8iRWOm/iah3fI J5dI0FhQTimhwNJ2rcvoDw95OK9CSrkSC5P6h4EuKB8LBuecMDSOMFb1PhXnOnJp ee3jM/GgoweWk2EMEW90vM5jq3jhLTkRC4/klgbKqD5kF/RzlpmXVDf8JXJeP+Q3 Y2oKz7APwr4jFTq1K2jNy1n55qIz43SUXsq2eUIoLhFMpo8NmQ8rA+/vIIPBTt8S gpNTOBeTsgu7IofcXHTleiLseUZn2AiQEYCt45M2xp6+sfeb1mJZk9fpKuUb650/ 4DeNCQAxee+nTs1gqybRVh6bLsM8o28aFEWqu1m89cLrESaUfLooVn7UpMuNQy2j 5x7kxxiNUJG1byHwAV8xATq3J1GDxRhNeM0wuxLvoH6fje8El0c= =4Z4m -----END PGP SIGNATURE----- --GCiYkmPM1sA5/Ovk--