Re: Pg_repack

Pahu,

I asked about VACUUM, not VACUUM FULL.

On Tue, Jul 23, 2024 at 1:36 AM Deepak Pahuja . <deepakpahuja(at)hotmail(dot)com>
wrote:

> Hi John
>
> Vacuum full generally takes very long time on large tables and also does
> exclusive lock on table causing it unavailable.
> Moreover it generates huge wal files and causes replication lag on
> secondary in streaming replication setup.
> Pg_repacknis online and removes complete bloating.
>
> But experts can tell more.
>
> Thanks
>
> Sent from Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------
> *From:* Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
> *Sent:* Tuesday, July 23, 2024 1:28:28 PM
> *To:* Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
> *Subject:* Re: Pg_repack
>
> On Tue, Jul 23, 2024 at 1:22 AM Sathish Reddy <
> sathishreddy(dot)postgresql(at)gmail(dot)com> wrote:
>
> Hi
> I am trying to schedule pg_repack from pg_cron in RDS postgres
> environment on avoid the bash on host EC2 to run run directly with in
> postgres instance.it getting successful but not clearing bloat by using
> repack fuction in pg_repack extension.please help on these to sort out .
>
>
> Out of curiosity, why do you feel the need to regularly run pg_repack?
> IOW, why doesn't plain old VACUUM suit your needs?
>
>