Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbIFH-00FUcB-F1 for pgsql-admin@arkaria.postgresql.org; Tue, 06 Aug 2024 11:20:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sbIFF-00ET3G-B0 for pgsql-admin@arkaria.postgresql.org; Tue, 06 Aug 2024 11:20:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sbIFE-00ET38-VC for pgsql-admin@lists.postgresql.org; Tue, 06 Aug 2024 11:20:48 +0000 Received: from mail-oa1-x33.google.com ([2001:4860:4864:20::33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sbIFC-003MxF-El for pgsql-admin@lists.postgresql.org; Tue, 06 Aug 2024 11:20:47 +0000 Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-268a9645e72so273236fac.1 for ; Tue, 06 Aug 2024 04:20:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722943245; x=1723548045; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lXvwf+I5ugNhAgFXZ7kIBEY+nco40FueJwm21JqHfjE=; b=XjmYBEWa8dKJDNPIp59GmUbwpXaZiTkttMt4m4oUE4AtV28Idqfp1Nl9rFX72s09aJ sEHhLAUOHdjUeF74xpmPu8tR4tOUhADGb5ZZXxdRrxY2rTTA/YGMouUmw3RoiD+xrBJT 3S73yY1sFhcFZVbHAnEWqGmkjDjCFSD+SKZ+tVKsUweVVIDCI+Pf5KnjNNOIdBz6OaXh cQApnpSTOVAr35aWQJEidWOz9LLJPWwBKZ1B+UjAT4qpzlutESE4Cj76sjQc0bGl+UNT x6vs1+G3mLX+J14qKp5y9hxNnQiRlnUvlLMIUGGPghfJdh+0LD3PrXJIwRBvEPkOJVx/ Fj9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722943245; x=1723548045; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lXvwf+I5ugNhAgFXZ7kIBEY+nco40FueJwm21JqHfjE=; b=sElEi7X/3lBzQkwxJBwv26Mdza38A1qbj4A60Ly+IpyD1p32ijgswv0hghqYilh1hu AotQzubwwCV3Fk7V1W3pwryhQ3PKEcF9ncfWQWsdzlDokk5BxewyPM/O7mLEZnBdSr38 n8FUfb1cAEMIEIQtNqdNdKIOf0vutCXvl46ky4nB5uZbAw94JwJ1xDXA0OfMIwkVLTS2 7GJ+VoeRBL6N7aSqO8bJt97Fg2l6HC8uUr4MI8DUV5faR/UVIXyx6gskf1RuI2GGPOEv gf9KV3HwtqDl+EltM7V4kmNP+EK7XpcAkqQSrhd880Oxwys6bGKq44izlNeiyHBgjbQX UGBQ== X-Gm-Message-State: AOJu0YwVN4XQmEckvAVFE1cxdIMH6tL6e+i7/ovi7nDfdgRRYMd/zBK/ M3oDhPrU1ws7Rgk8lUYoi0mrrLpDuSH0UoRai28SgxkFZhHCUtSxfSMTmXzAAsO716m1BtMRqxt Ihi+oaJCj4dgx5xkwAwgmkNt3AAeNOA== X-Google-Smtp-Source: AGHT+IEwaQfnvRpNEMAMhrHwgBB/jKZ1DCvFvH3uQhmKgtHtAU6ZRijBr/JD1U7EirDBTlABqMUqk9sDM4N33Vgg9xo= X-Received: by 2002:a05:6870:ac10:b0:260:f50e:923f with SMTP id 586e51a60fabf-26891edb6ccmr18790733fac.42.1722943245391; Tue, 06 Aug 2024 04:20:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sathish Reddy Date: Tue, 6 Aug 2024 16:50:33 +0530 Message-ID: Subject: Re: Pg_repack To: depesz@depesz.com Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000001c1cf3061f01fcce" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001c1cf3061f01fcce Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFPM hubert depesz lubaczewski 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 > > --0000000000001c1cf3061f01fcce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Thanks for the information.please provide me solution on cle= aring 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 lev= el with in postgres..

Thanks
Sathishreddy


On Tue= , Aug 6, 2024, 4:45=E2=80=AFPM hubert depesz lubaczewski <depesz@depesz.com> wrote:
On Tue, Aug 06, 2024 at 04:39:53PM +0530, Sathish Redd= y wrote:
>=C2=A0 =C2=A0We planning to create store procedure (function) in postgr= es database to
> run pg_repack on removing bloating of table or index by using within > postgres instance.
>=C2=A0 =C2=A0 =C2=A0Please 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.<= br>
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

--0000000000001c1cf3061f01fcce--