Received: from malur.postgresql.org ([2a02:16a8:dc51::56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1fScVK-0004aN-3y
	for pgsql-admin@arkaria.postgresql.org; Tue, 12 Jun 2018 06:10:06 +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 1fScVH-0007Ze-Of
	for pgsql-admin@arkaria.postgresql.org; Tue, 12 Jun 2018 06:10:03 +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_SHA384:256)
	(Exim 4.89)
	(envelope-from <pavan.postgresdba@gmail.com>)
	id 1fScVH-0007ZU-HA
	for pgsql-admin@lists.postgresql.org; Tue, 12 Jun 2018 06:10:03 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by magus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pavan.postgresdba@gmail.com>)
	id 1fScVA-0001Wz-Kb
	for pgsql-admin@postgresql.org; Tue, 12 Jun 2018 06:10:03 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id 07FAFD6C8AC1
	for <pgsql-admin@postgresql.org>; Mon, 11 Jun 2018 23:09:55 -0700 (MST)
Date: Mon, 11 Jun 2018 23:09:55 -0700 (MST)
From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-admin@postgresql.org
Message-ID: <1528783795029-0.post@n3.nabble.com>
In-Reply-To: 
 <CACh9nsYOacwJ6D_sVenarjpVNNXgDdhSP-bFpdXVmoms5fkLOw@mail.gmail.com>
References: <1528723690634-0.post@n3.nabble.com>
 <477ADE32-3CCE-4A9A-A286-ADDAB0B4F74B@icloud.com>
 <CACh9nsZ9EmeEZv3u1s+iDQ6stv5+ARi=pWvz0hXaOMW4izFrPQ@mail.gmail.com>
 <A7B2C6A7-22A0-40DC-8C2C-963C8AFDEA87@icloud.com>
 <CACh9nsYgS6-5YO8bp7uex9WUTu2XwFNHGbP=aR5DkQoO4NPwHA@mail.gmail.com>
 <B7E2FA3A-5D81-4EBD-977E-1958520298AE@icloud.com>
 <CACh9nsYOacwJ6D_sVenarjpVNNXgDdhSP-bFpdXVmoms5fkLOw@mail.gmail.com>
Subject: Re: PostgreSQL 'Corruption & Fragmentation' detection and
 resolution/fix
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

Hi,

Can we get any information regarding fragmentation/corruption in the
database level from the system table 

"Information_schema.columns" ?  

Actually my strong belief is  other databases like SQL server, Oracle &
Mysql are providing some system views to detect corruption and fragmentation
from the database. So thinking the same with the postgres.

As I was asked to prepare a script well in advance to predict the
forthcoming disasters

Regards,
Pavan



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html