Re: Pg_repack - Mailing list pgsql-admin

From Ron Johnson
Subject Re: Pg_repack
Date
Msg-id CANzqJaDTqThyqB-tNAbLdJ+Pt2o1MER519dtsSuifAdAM_kuCA@mail.gmail.com
Whole thread Raw
In response to Re: Pg_repack  ("Deepak Pahuja ." <deepakpahuja@hotmail.com>)
List pgsql-admin
Pahu,

I asked about VACUUM, not VACUUM FULL.

On Tue, Jul 23, 2024 at 1:36 AM Deepak Pahuja . <deepakpahuja@hotmail.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 

From: Ron Johnson <ronljohnsonjr@gmail.com>
Sent: Tuesday, July 23, 2024 1:28:28 PM
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Pg_repack
 
On Tue, Jul 23, 2024 at 1:22 AM Sathish Reddy <sathishreddy.postgresql@gmail.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?
 

pgsql-admin by date:

Previous
From: Muhammad Imtiaz
Date:
Subject: Re: WAL file corruption on standby PostgreSQL
Next
From: Somnath Som
Date:
Subject: pg_basebackup not completing