From: Thomas Kellerer <shammat@gmx.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Maintenance
Date: Wed, 8 May 2024 14:02:45 +0200
Message-ID: <8f36cff9-78aa-4e72-ab22-093a889a926d@gmx.net> (raw)
In-Reply-To: <CAEQOu1Fu2i7EoimtG_T4FQkuN5z3L5pY6n4jHHk=xB+NWZMfMw@mail.gmail.com>
References: <CAEQOu1Fu2i7EoimtG_T4FQkuN5z3L5pY6n4jHHk=xB+NWZMfMw@mail.gmail.com>
Sunil Jadhav schrieb am 08.05.2024 um 11:17:
> We have a 12TB db and one table having around 7 TB data , is there
> any option we can removed the dead tuple and size also increase for
> that partition without downtime . Vaccum full we can't do because of
> exclusive lock in tables during processing.
>
> We have critical application so don't get the downtown so how to
> achieve this please let us know
Have a look at pg_squeeze or pg_repack but both will create a copy of the table,
so if you don't have enough free disk space neither is an option.
You probably also want to investigate if making autovacuum more aggressive
helps
Did you validate that those dead tuples you see really are a problem and
are not re-used?
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: shammat@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: Maintenance
In-Reply-To: <8f36cff9-78aa-4e72-ab22-093a889a926d@gmx.net>
* 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