Message-ID: <2f4c4edac9196af943d8097150f65fa96f7ea97e.camel@cybertec.at>
Subject: Re: Table health
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Wed, 18 Oct 2023 08:52:41 +0200
In-Reply-To: 
 <CAJk5AtbS6c-P+YzmSa=2jU=vSavUk1Or=3DEd++3iAJT+-UCDg@mail.gmail.com>
References: 
	<CAJk5AtbS6c-P+YzmSa=2jU=vSavUk1Or=3DEd++3iAJT+-UCDg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/2f4c4edac9196af943d8097150f65fa96f7ea97e.camel%40cybertec.at>
Precedence: bulk

On Tue, 2023-10-17 at 23:23 +0530, Rajesh Kumar wrote:
> I have been asked to check table health of specific big table.
>=20
> What are list of things I have to check?

Look at pg_stat_all_tables to see if the number of dead tuples
is excessive and if autovacuum and autoanalyze are running as
they should.

Look at pg_class to see if "relfrozenxid" and "relminmxid" are
far from the danger zone.

Run the function pgstattuple_approx() to see if the table is bloated.

Yours,
Laurenz Albe