Date: Tue, 6 Aug 2024 13:22:21 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Sathish Reddy <sathishreddy.postgresql@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Pg_repack
Message-ID: <ZrIHbeg5TwL9etUn@depesz.com>
Reply-To: depesz@depesz.com
References: 
 <CA+M9Y+A7mUFRELeOu0g-3J+bgvf_wmuyhb+rE9X3KvLr7XQh9w@mail.gmail.com>
 <ZrIF1SiEGC_Ghsrr@depesz.com>
 <CA+M9Y+DuP6XKh8OZiv4SSp-FwVOKp6-NrgLMAKerBL31Oo7iOw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: 
 <CA+M9Y+DuP6XKh8OZiv4SSp-FwVOKp6-NrgLMAKerBL31Oo7iOw@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ZrIHbeg5TwL9etUn%40depesz.com>
Precedence: bulk

On Tue, Aug 06, 2024 at 04:50:33PM +0530, Sathish Reddy wrote:
> Thanks for the information.please provide me solution on clearing bloating
> on table or index bloating with out blocking any user and we are not run
> any vaccum full .freeze, and reindex and also analized ...with out these
> provide me perfect solution to run and remove bloat instance level with in
> postgres..

1. Configure autovacuum properly, so the problem doesn't happen.
2. If need is - run manual vacuum
3. If you really have to, run pg_repack - but this is not a thing that
   one calls *from within pg* - you run it on some
   server/computer/whatever, and pg_repack connects to database, and
   does its magic.

Best regards,

depesz