From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Table health
Date: Wed, 18 Oct 2023 16:13:55 +0200
Message-ID: <202310181413.czntq43lzvfu@alvherre.pgsql> (raw)
In-Reply-To: <CAJk5AtbS6c-P+YzmSa=2jU=vSavUk1Or=3DEd++3iAJT+-UCDg@mail.gmail.com>
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@alvh.no-ip.org, rajeshkumar.dba09@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Table health
In-Reply-To: <202310181413.czntq43lzvfu@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox