Re: Pg_repack

From: "Deepak Pahuja (dot)" <deepakpahuja(at)hotmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Pg_repack
Date: 2024-07-23 05:36:04
Message-ID: PH0PR19MB55730F2DC8CD94C1634C77B3D6A92@PH0PR19MB5573.namprd19.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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<mailto: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<http://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?

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message khan Affan 2024-07-23 05:43:10 Re: Pg_repack
Previous Message Ron Johnson 2024-07-23 05:28:28 Re: Pg_repack