Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qnwFe-00CTaF-BF for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Oct 2023 07:24:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qnwFc-00D2ti-OR for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Oct 2023 07:24:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qnwFb-00D2tZ-8h for pgsql-bugs@lists.postgresql.org; Wed, 04 Oct 2023 07:24:56 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qnwFY-0086te-GE for pgsql-bugs@lists.postgresql.org; Wed, 04 Oct 2023 07:24:54 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailout.nyi.internal (Postfix) with ESMTP id 186985C02F0; Wed, 4 Oct 2023 03:24:51 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 04 Oct 2023 03:24:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type: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=fm2; t=1696404291; x=1696490691; bh=6k R0NCT+0aSm3LiH7+dLuYjfKXEN6dHT6Djc0Aa6ZMI=; b=jIacRSoosCGz/gGAaL 7h/4VdS6ECAfN9xA0opx2FjQj3QHqUkDO6sKWs2ZMZYsWYUFTAUfN9hbvnk1vhay OGzaHrqBMc8KpO6CS6JccpbblR3ijBsgFn+XqMq0Umqlic9h/ky2TyA7OS4RO2+/ 2Mdc1JmH1eZK/SXIlDTutVv6pC4cZlB0DYd25UyxqT+5anSbdh73PMxh+mkav7pF IATP0CihJn1DeRRILPoXtI/zFn3GZqWJsUNAT/fmlslHW5bkDvG+8BTxButPMGl3 aNgg2l4Jfnp0u6gg1KAETTvlzG+2HyuZvf1YaqNMo37Aks5qV/912hGZnlAY587J 1ErA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type: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=fm2; t=1696404291; x=1696490691; bh=6kR0NCT+0aSm3 LiH7+dLuYjfKXEN6dHT6Djc0Aa6ZMI=; b=rbhnhMjqi06VFsuEPBblsGRhGxWcq Ut7UQU3nRC7P4rSPUdXR3QRhZLKnCJxSpCtgDsoOm852QynaMz8ykPpy7ZGHAvJ8 qhEWUzZXtv2dpV83ishVKYGiedHxSe0s8PUdO9a2MfnucyoAqF8DNJkaFZ9wcnpv sbB0Zok2YnY96fkZLxYLM142mNkU33EaesopoD01reQI7Zta+AR/cAxeNT0BJTV7 DYSDGRbXaBJzRQn2UqHBbhWkPvw+vsQknz9opCXc4F1yuSSuAeybVYQuOY44F88Z O58rUefek7I/wbJKbdRFGaFPj1MosxA4q5Z2boSVTiGlLyVIndnqr9g6A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrgedugdduiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeetleeifedufffhhfdtteelgeeg geffhfekueevteeigfduudevudetgfegiedvjeenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 4 Oct 2023 03:24:49 -0400 (EDT) Date: Wed, 4 Oct 2023 16:24:45 +0900 From: Michael Paquier To: Laurenz Albe Cc: rootcause000@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Message-ID: References: <18146-04e908c662113ad5@postgresql.org> <9fc4118d2a8f2290d8598a9c4d451c4c90b17cee.camel@cybertec.at> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="M6inExeiB404z5LS" Content-Disposition: inline In-Reply-To: <9fc4118d2a8f2290d8598a9c4d451c4c90b17cee.camel@cybertec.at> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --M6inExeiB404z5LS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Oct 04, 2023 at 09:17:11AM +0200, Laurenz Albe wrote: > Data corruption like this is not necessarily caused by a PostgreSQL bug. Err, well... A failure on the end-of-vacuum truncation should not lead to corruption afterwards as well, and this ought to be safe even if this step failed. This is a very tricky problem that nobody has really looked into yet. -- Michael --M6inExeiB404z5LS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmUdEz0ACgkQnvQgOdby QH1WLBAAgJrc6XFBq8oDQh/KD6KJsLF4XsL4nd7LMIBk+G+ln3mbADrRishv4sZV NhLdzo0vhOZMnUpvSTlJliVFEtBTsA2g47syElJkCfiWSQK2rmZX92PSqYFeaTc3 YOJCp291qNosnqwlJMVOETdkED7S/I8HhUD+wfpM9Grdvrv8qv2S2lHmG9FJwswf 1IibAwSMK4ZC5ACPScXyYm/dp7MJ8a9raTrY6sasG6mmA93kqXTFH3iCAkE6GRM7 1vuAH1w8rBtOWAH355I3fVwU1OUbFg5aT85yTqjbNQxdjE58jJ0SM36abjo6Dylc oFpvH92WVZbeW+fBV3V7AO+jKtg350sWu5Eh8Jlazor4GWH6oB6XZQ89sCEK5xwk gL7RQX3wPXhcUjE3DTFXFP7DOKbuo9xDP6+vZ22pofN9yFygfjD2+5+cgAkBcqS+ baUJSrI1w3rsvRn07d/m6CV9nBfX+3ezF7aVmFDyuVLQtc7773j3NY+oTWPrK2Y3 qGoJSf3mcMLKoELH8MwMGxj9ODvRdWo0LcC3yZtjRC9HZkM2xHq8AwgNpRisDpJi 5Xxs8AHY2ycq58mZhk/M0DkaOUWhLzk2WXFWo7cXa9JCtpHpRLwK/jjJM67y9YC2 ezrbBRh4I0623K2ByB9yVauDCoE+jzfbN6nj42VOXNV6fgfFckw= =oF48 -----END PGP SIGNATURE----- --M6inExeiB404z5LS--