Date: Tue, 6 Aug 2024 13:15:33 +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: <ZrIF1SiEGC_Ghsrr@depesz.com>
Reply-To: depesz@depesz.com
References: 
 <CA+M9Y+A7mUFRELeOu0g-3J+bgvf_wmuyhb+rE9X3KvLr7XQh9w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: 
 <CA+M9Y+A7mUFRELeOu0g-3J+bgvf_wmuyhb+rE9X3KvLr7XQh9w@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ZrIF1SiEGC_Ghsrr%40depesz.com>
Precedence: bulk

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