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 1qt7JT-00AuU9-Of for pgsql-admin@arkaria.postgresql.org; Wed, 18 Oct 2023 14:14:20 +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 1qt7JR-004YVC-GE for pgsql-admin@arkaria.postgresql.org; Wed, 18 Oct 2023 14:14:18 +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 1qt7JQ-004YSf-9C for pgsql-admin@lists.postgresql.org; Wed, 18 Oct 2023 14:14:17 +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 1qt7JN-0016EM-IQ for pgsql-admin@lists.postgresql.org; Wed, 18 Oct 2023 14:14:15 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A4DBC5C02F2; Wed, 18 Oct 2023 10:14:11 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 18 Oct 2023 10:14:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :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=1697638451; x= 1697724851; bh=R4ylu7UHLe3AO214PRAxqCwxtVRA42nRCF+SV/0EOrk=; b=k ApdmkK9hSjyH7CBjWjR9qy4ABLy9BMrGzkoC0zEwVwCNQPSeZycYqY8G9kWNu2Zx w+95g2R+ieQ/8dRuCq9GnFdYOdAKvBbYaEJGIqFLeQmpjJNah8EZyhWrNjobSJne g1p4MlYvNZ+j6vBZdMd4yVYdKMZHq777kSHsOBFiEe7X06RRFq08WsuFjulL8yoh l5bmlRPH5z+n2nsedB8W9YsiCVIsP06dF1BqzzvTQChfmIVoUMAo4mlblmt6A31N iFhVr9NoigiarOfhzPSE9ftd6ovzVJeX7AFrWshNFk664dw4Ux6FWkordaBiNsow jNlXY0FkbopiF5ogk5DLA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrjeeggdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvfevuffkgggtugfgjgesthekre dttddtjeenucfhrhhomheptehlvhgrrhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgv segrlhhvhhdrnhhoqdhiphdrohhrgheqnecuggftrfgrthhtvghrnhepvdektdffudfftd ffffehfffhjeejhffgieeuueekjeekfffgudffhfduffffueevnecuffhomhgrihhnpegv nhhtvghrphhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 18 Oct 2023 10:14:10 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1697638435; bh=Y24NmUwJDPYIysOLJV0H/cR9yUSfCnstgRBczCeoDqI=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=SKFh9EL0FCdBf1fUjP0saYy9wfgV31Vk2Kp/iYdcHjxou2Wxe/EhYQWr3GpQzWoF7 ABMlXVbk7U5RvX4lvPx9NeiIvaqvst2jfX2wAe/+cQZtHQ2I3IZLscKwVT4tIZ20rf MV4lnS3F3CfLtEjPtZoJQnmKMtb7MRfUWr1Y/J+wb6I3Wh4oDn4vM7fp7j6EoN5WNF qS2UMlQjpd6DXOx+oJEICJcwHKisjqzdXTewjff1IJwFFJaPdZ4CZ43BDFrAcYcFOO 8aIXMKVgbDi51o4Q+3fAWPDbuoykpwsbj6CCS6nl0BXMeTyNIKiwIB/3vFTsH2zbHT RZqxSspfJAUjw== Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 1C61DBD; Wed, 18 Oct 2023 16:13:55 +0200 (CEST) Date: Wed, 18 Oct 2023 16:13:55 +0200 From: Alvaro Herrera To: Rajesh Kumar Cc: Pgsql-admin Subject: Re: Table health Message-ID: <202310181413.czntq43lzvfu@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Oct-17, Rajesh Kumar wrote: > I have been asked to check table health of specific big table. > > What are list of things I have to check? Install extension pg_visibility and run functions pg_check_frozen and pg_check_visible on the table. I've seen a couple of cases of **serious** data recoverability issues that aren't discovered until much later, caused by pages having been improperly marked all-frozen in some distant past. I assume it's possible to have pages marked as all-visible as well, which would cause different issues. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Aprender sin pensar es inútil; pensar sin aprender, peligroso" (Confucio)