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 1kQgKn-0001Du-2t for pgsql-bugs@arkaria.postgresql.org; Fri, 09 Oct 2020 00:32:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kQgKk-0008B8-7T for pgsql-bugs@arkaria.postgresql.org; Fri, 09 Oct 2020 00:32:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kQgKk-0008B1-1P for pgsql-bugs@lists.postgresql.org; Fri, 09 Oct 2020 00:32:30 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kQgKh-00036e-TU for pgsql-bugs@lists.postgresql.org; Fri, 09 Oct 2020 00:32:29 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A67615C012F; Thu, 8 Oct 2020 20:32:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 08 Oct 2020 20:32:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=rPNL7LIgIWIwq5NIP/autv1uWLd 4gO883ZEM4FY0olU=; b=InOiY9DZeQT60cxkJWlZx03VOimQYstx89EXCzDV7f/ RV2z1Tz7dkmjuL+fkNrukdOF9eJ6HJJUVk0XY2srO3MSqfpytD8DiuQpmiTBu2T6 Uy6n5xp2omEm/KVmNuAS54lt9Kc0e6U8hJTndUjwd9Lx8cwldTc+F6p4yu5p+hyp Jx42g6gIIed59Uq/bYAFMtHgR/wou43aYXQkIWLNfuWnkU3bnxEaSf1brAdw5bqw SQvpUVHUqoVyq507rg0mXpEFBfe/Y3/9NHYXPMSmK8hMIFBsXrWypqo0WH/FAV4l dGP9l2Lg1A4eWyluH8vH9hoLSKwIa/6O4SiKW4FG0FQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rPNL7L IgIWIwq5NIP/autv1uWLd4gO883ZEM4FY0olU=; b=baD2tLhMfyD/Zcyk2pI1Ng Ym9CXHWtXjf28MlKdxqGrOOJP/02fS5wR5vCV6pV5Sw1+h/CWJIsdWWOoQ/7JQTQ so0Lr/VWTpp9hTZEoI4CXuvSiX2d8joCg1HfvTxDpnVvFMwjkjmPGwyhvPcFRJht bfNZzJPQpOTMmMWXmLm0v0q/43s572T6yJ/ef9CPpxfaZ2Qwbj8oFVvbh1IlWgPx fnNYH0GAV607asOUHRaeH8BLaZ/sFQo9AJD62Pq9le3zxmeZROqSq0ACL8GgVCVU l2DrYfsRuCqi2WqIT4zTC/85qcKXgaxx16tHR8H1Ng2O9HxIAsKQAycw8+gQDGrg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrhedtgdefiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdejtddmnecujfgurhepfffhvf fukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhi vghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnh epvdegudeuhfdtueeltedtveejheehieevueeigeelteegleejleeiueeiheegvefhnecu kfhppeduuddurddutddvrddukedtrddukeehnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id 2DA293064680; Thu, 8 Oct 2020 20:32:24 -0400 (EDT) Date: Fri, 9 Oct 2020 09:32:22 +0900 From: Michael Paquier To: 1726002692@qq.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16662: pgbench: error: client 418 script 0 aborted in command 5 query 0: ERROR: invalid page in block 4830 Message-ID: <20201009003222.GC1528@paquier.xyz> References: <16662-3a8edb25b118fb28@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="V88s5gaDVPzZ0KCq" Content-Disposition: inline In-Reply-To: <16662-3a8edb25b118fb28@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --V88s5gaDVPzZ0KCq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Oct 08, 2020 at 03:49:58PM +0000, PG Bug reporting form wrote: > During the pressure test using pgbench, the following error occurred, but > the object with oid=16396 was queried through pg_class, and it did not > exist. Is this a bug? Unlikely one in Postgres itself, I would recommend to be very careful with this instance :( A data checksum failure, as the one you are seeing here, means that an 8k page of a relation file that Postgres has flushed out to disk in the past has been loaded back with some unexpected data. This means that a source external to Postgres has changed this data. I have seen this class of failures with problems involving either the kernel, the file system, the hardware, or even some layer in charge of the host virtualization, if your host is a VM of course. So something has likely managed the flush request thought as completed by Postgres in a non-durable way, or something could have directly changed the on-disk data with the flush request actually done correctly, which is even a worse problem. What this error tells is that the problem does not come from Postgres itself. -- Michael --V88s5gaDVPzZ0KCq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl9/r5YACgkQnvQgOdby QH1I9w//QuQE/tL6EvCMAGzWQVVuq7WCtUBZHXEas01X5LkS40NR22c5dvle9IpU 4Ej/OXybBlZZ9Xhd66a1JipTfY5xIc9QrYbOztm/1o29+5p/fuMtcv42X+f5p5Vg 4nwNhy9oiSyKa+d78yl/mfsqawPaWPQyy95YjaK84ic+P/8rmDktemxJCajeLzc2 b+1zJDHC91gKz22GrMwY+z7HRp4Dk02YibADPQFB4x/2el5aapo8X/Ldo1Npe9z3 cgVzTNHS34wEALANS3qLXiFJ9tdBmzEDF4qmAcwbzF1TRs1EpC5d9iGEhonR7XZz uQivFRw2bLoKjQ9ibyKu+0lms/wNe0v0LECXokook3uPcVeMCJBkITtcbsDvWDW/ euPGtBMZGxqMHMM3GA56hXJe5CO27cIqeysQPBJbE2DGppR9s+JnHIdIy86g5kG1 eYxKEHrzlY9th5qsRGS/d6HGquFDCfNGxqldpItXBm4Y8ag6VCsrr6dJNbvYVRLn I9/GZ4KjVOilFLSRiNZn5QSC9ikKdXdc65vYIAwAg1PCyOSjvvPNwVlQdRQaTV9R sJSF73exqQRsQNPBR1J9ub2EDrNb0x+1/sG6dMvgfXEn+fzSbum3SOuSDqb+lS13 VLi+AnOy3zND2xi49mBAcKmrq2Y7de0vEdYCUEOibnu3qTg475E= =QdfV -----END PGP SIGNATURE----- --V88s5gaDVPzZ0KCq--