Re: Pg_repack

From: abbas alizadeh <ramkly(at)yahoo(dot)com>
To: Sathish Reddy <sathishreddy(dot)postgresql(at)gmail(dot)com>
Cc: depesz(at)depesz(dot)com, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Pg_repack
Date: 2024-08-06 11:24:28
Message-ID: BBA040D2-0FAB-4B68-807F-5213E0D7A58D@yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi

Why you don’t use pg_squeeze?

It has its own scheduling to remove bloating.


Regards

Abbas




On 6 Aug 2024, at 2:51 PM, Sathish Reddy <sathishreddy(dot)postgresql(at)gmail(dot)com> 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..


Thanks

Sathishreddy



On Tue, Aug 6, 2024, 4:45 PM hubert depesz lubaczewski <depesz(at)depesz(dot)com> wrote:



On Tue, Aug 06, 2024 at 04:39:53PM +0530, Sathish Reddy wrote:

>   We planning to create store procedure (function) in postgres database to

> run pg_repack on removing bloating of table or index by using within

> postgres instance.

>     Please help me on details on steps with example for same.

That will be impossible and/or hard.

The problem is that stored procedure/functions runs in database. and

pg_repack is external program, that *does stuff in database*, but it not

*all* in database.

It's kinda as if you wanted to make stored procedure to run photoshop.

You can kinda work around it by using some PL/* language that allows

external program execution, but it is extremely unlikely to do what

you'd think it will do.

Best regards,

depesz




In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kashif Zeeshan 2024-08-06 11:24:57 Re: Pg_repack
Previous Message hubert depesz lubaczewski 2024-08-06 11:22:21 Re: Pg_repack