Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSqOx-0003a6-CQ for pgsql-admin@arkaria.postgresql.org; Thu, 07 Nov 2019 22:37:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSqOw-0003yX-6G for pgsql-admin@arkaria.postgresql.org; Thu, 07 Nov 2019 22:37:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSqOv-0003yO-K6 for pgsql-admin@lists.postgresql.org; Thu, 07 Nov 2019 22:37:13 +0000 Received: from cyclops.postgrespro.ru ([93.174.131.138] helo=mail.postgrespro.ru) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1iSqOo-0008Iq-8b for pgsql-admin@lists.postgresql.org; Thu, 07 Nov 2019 22:37:12 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 03B3821C49B0 for ; Fri, 8 Nov 2019 01:37:04 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=x tagged_above=-99 required=4 WHITELISTED tests=[] autolearn=unavailable Received: from [192.168.3.134] (broadband-95-84-150-205.ip.moscow.rt.ru [95.84.150.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id CA83421C49AD for ; Fri, 8 Nov 2019 01:37:03 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1573166223; bh=x28DgL4M0cGUf8asipUCZQMisp6l+gGy/eAjC0pxRww=; h=Subject:To:References:From:Date:In-Reply-To; b=dxzhomVmrQDvc/ujlgYUR/oCtTONvBIt2ktF6IFMz48JNRbe43f77J+m5k3FkFv/e TvbTGv+EJjhrmsd5ki4G4yVMJbzWtKOvMe1BIV71hIQqo2/8CW8H1XSCDhSTV819vG dlVSUB4+tBR92q2nE2/nC8ULeinKySjMdjx1XS3Q= Subject: Re: Database consistency check. To: pgsql-admin@lists.postgresql.org References: From: Grigory Smolkin Message-ID: <26d7d056-5424-7f4d-ddf9-d74896c7e0ac@postgrespro.ru> Date: Fri, 8 Nov 2019 01:37:03 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello! pg_probackup has dedicated command for PostgreSQL instance verification, which rely on amcheck, page checksum comparison and page header sanity checks. It can be used on running databases and can be used even if you do not use pg_probackup for backup/restore purposes. https://github.com/postgrespro/pg_probackup/blob/master/Documentation.md#checkdb https://github.com/postgrespro/pg_probackup/blob/master/Documentation.md#verifying-a-cluster On 11/7/19 10:47 AM, Asomba Djala wrote: > Hello, > > I have a question, SQL Server has a tool DBCC checkdb and I believe > Oracle it's VerifyDB. Does Postgres have something similar and if not, > does anyone have steps or queries to do a sanity check or database > integrity check with PgAdmin4? > > In advance, > > Thank you for your help. > > Aso. -- Grigory Smolkin Postgres Professional: http://www.postgrespro.com The Russian Postgres Company