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 <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1iSnpZ-0005n4-Gf
	for pgsql-admin@arkaria.postgresql.org; Thu, 07 Nov 2019 19:52:33 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1iSnpY-0004H3-9B
	for pgsql-admin@arkaria.postgresql.org; Thu, 07 Nov 2019 19:52:32 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1iSnpX-0004Gw-WB
	for pgsql-admin@lists.postgresql.org; Thu, 07 Nov 2019 19:52:32 +0000
Received: from mailout.easymail.ca ([64.68.200.34])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1iSnpQ-0003gA-70
	for pgsql-admin@postgresql.org; Thu, 07 Nov 2019 19:52:30 +0000
Received: from localhost (localhost [127.0.0.1])
	by mailout.easymail.ca (Postfix) with ESMTP id 54BB6A0B5A;
	Thu,  7 Nov 2019 19:52:22 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at emo05-pco.easydns.vpn
Received: from mailout.easymail.ca ([127.0.0.1])
	by localhost (emo05-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VC7-i_EhLqes; Thu,  7 Nov 2019 19:52:22 +0000 (UTC)
Received: from shr-macbook-pro.local (unknown [8.39.228.117])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mailout.easymail.ca (Postfix) with ESMTPSA id 5EC61A096B;
	Thu,  7 Nov 2019 19:52:18 +0000 (UTC)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Database consistency check.
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CAOdgZeTDy_KeqTZE9evxrSKJyV-LkFgcniKtRk2xsR0ftkZEkQ@mail.gmail.com>
Date: Thu, 7 Nov 2019 12:52:17 -0700
Cc: abbas alizadeh <ramkly@yahoo.com>,
 pgsql-admin <pgsql-admin@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9549E91-756F-4726-9EB0-A35FC7A292F8@elevated-dev.com>
References: 
 <CAOdgZeRFyXPL4knBetHsqWmk2OMauvqK5RoWcU7gOGF82HCzyQ@mail.gmail.com>
 <632596C8-5333-478E-8C4C-1CE486DC339F@yahoo.com>
 <CAOdgZeTDy_KeqTZE9evxrSKJyV-LkFgcniKtRk2xsR0ftkZEkQ@mail.gmail.com>
To: Asomba Djala <asombadjala8@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

> On Nov 7, 2019, at 12:16 PM, Asomba Djala <asombadjala8@gmail.com> =
wrote:
>=20
> Thank you. What about already initialized clusters?

I believe PG 12 adds the feature that checksums can be added to existing =
clusters???

Probably requires taking the cluster down, and won't detect existing =
corruption...