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 1sVl9e-00BV8c-6H for pgsql-general@arkaria.postgresql.org; Mon, 22 Jul 2024 05:00:10 +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 1sVl9c-00EsoJ-2v for pgsql-general@arkaria.postgresql.org; Mon, 22 Jul 2024 05:00:08 +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 1sVl9b-00Eso3-JW for pgsql-general@lists.postgresql.org; Mon, 22 Jul 2024 05:00:08 +0000 Received: from mail-qv1-xf30.google.com ([2607:f8b0:4864:20::f30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sVl9Z-000ng1-1O for pgsql-general@lists.postgresql.org; Mon, 22 Jul 2024 05:00:06 +0000 Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-6b796667348so31575926d6.0 for ; Sun, 21 Jul 2024 22:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721624404; x=1722229204; 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=rW7mt4SRboGeO7s37hWDRytJLIt+KL5bszGGvDMN6ds=; b=c01OOaAkw1zABlyXl+0SCpQt5n8TNmK2AqKrsUjuxJAaw1QvmpbMFaDfV8Vv0CLBxU V/rtglnJk62T//6uIWxVHOlIGoEW9kJcRKSOKqhyRDG8uC1rhivgo6aRxbm1KfMkacOM hf+wIeXFbd5BEjB1/Unv2AO4YBwXJc8FYqWofGeQGC2UEKJCW3q5IVyp53lwuIbfHEiU Kdtga2fMN1H7MEVea6LJw1LWuLImIatCJD3mrA5/v23WkUloNyk0vhQHXhE4Uo4yxDd5 /2w8zEo8TdQuNJ4V5lXqzepuHh4is2mqvuFl8zAwjuVqfvMon9OpDseT5cy20Blz3Rbh 6LKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721624404; x=1722229204; 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=rW7mt4SRboGeO7s37hWDRytJLIt+KL5bszGGvDMN6ds=; b=I0yqjIhHxm09iKUXicOCGn6iHGzNeNAJemeiNZTFg6HJVvgrYT1xpEC47lI5GHSTTP 4RTUp/BCdWwoENJsWbU+OafGZuBOH1KZ/iaIwPRi4E7ns07I8y/jQBQx6s2otynbTplD 5hNUrQz33DqW10ESN4LEzBOIvs65KCXaDb1nWZgahQgcFyIbpqq9E74uNT+SVisH+sQQ xhr3NAdmDEWzz1vP/R2Sq6kooraVD3Bm25eOcZAptcKV7c9JM4BGiRlpcrTpMBUI3DU8 0k+lnKixlMsOsBIBuKdCttXaRfpNT3w9s8ENSHlSBgUFDhRI6jCl0N1rTmx5kI8TSbWi gy/Q== X-Forwarded-Encrypted: i=1; AJvYcCXY+sItI+9B3zEqx8xiv0pjdNuuqBob8//DXOhW9OLd25t0L1+EAynbMvCQ2zMbu1jbjZawR1gDo/rwPOWRsxDXh1f7Juy8VAf3mbRKUUDf7KQf X-Gm-Message-State: AOJu0Yzv7Slj/VKXwmAtSonXzEelZgvNUNGBxQjiMztLIocsoHnUZCk2 tyCpt0TwgGC8vXrnd1FOH91kaAtihnhSRNC0b/tp6cmDRgfi4Xeda/JZKAttpH0DkrZ9HtpZxH3 nAv8+Z7iYdzzKmVTqAb5Vphf44eE= X-Google-Smtp-Source: AGHT+IH3oY9f5bPI01J9BPR5/wKn3k1OvXwTGwCntPvzFXXxLpT4S23IOaa9FS8DxPXZMYvEXZWCssZqUbrVI7X1VLY= X-Received: by 2002:a0c:ef03:0:b0:6b7:9a0a:33db with SMTP id 6a1803df08f44-6b79cd276efmr278262926d6.23.1721624403904; Sun, 21 Jul 2024 22:00:03 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Muhammad Imtiaz Date: Mon, 22 Jul 2024 09:59:53 +0500 Message-ID: Subject: Re: Fwd: Regarding tables detach concurrently with run_maintenance_proc() To: Durgamahesh Manne Cc: Christoph Berg , pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org Content-Type: multipart/alternative; boundary="0000000000000810b9061dceeba4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000810b9061dceeba4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi , You can consider the pg_pathman extension. *Muhammad Imtiaz* *PostgreSQL Technical Support Lead * */ Pakistan R&D* *Mobile: +923345072521* *Email: imtiaz.m@bitnine.net * On Fri, Jul 19, 2024 at 7:55=E2=80=AFPM Durgamahesh Manne wrote: > > > On Fri, Jul 19, 2024 at 7:55=E2=80=AFPM Christoph Berg = wrote: > >> Re: Durgamahesh Manne >> > with pg_partman By default proc() does not detach tables concurrently. >> How >> > do we implement tables detach concurrently without blocking other >> sessions >> > Here queries not using date column to detach tables with >> > run_maintenance_proc() which is not using concurrently based on the >> > retention policy which leads to scan all available child tables hence >> need >> > to trigger this proc with concurrently option to avoid blocking other >> child >> > tables beyond rentention policy while running statements on them >> >> You might have more success by filing pg_partman issues at >> https://github.com/pgpartman/pg_partman/issues >> >> > Do we have any other alternative rather than using pg_partman()? >> >> Well you can just run the same commands manually that pg_partman would >> run. >> >> Christoph >> > > Hi > You might have more success by filing pg_partman issues at > https://github.com/pgpartman/pg_partman/issues >>> okay > My intention is to have any other extension other than pg_partman to > manage table partitions manually > > Regards > Durga Mahesh > --0000000000000810b9061dceeba4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi ,

You can consider the pg_pathman extension.
=

<= /table>

Muhammad Imtiaz

PostgreSQL Technical Supp= ort Lead=C2=A0/ Pakistan R&D

Mobile: +923345072521=

On Fri, Jul 19, 2024 at 7:55=E2=80=AFPM Durgamah= esh Manne <maheshpostgres9@= gmail.com> wrote:


On Fri, Jul 19, 2024 at 7:= 55=E2=80=AFPM Christoph Berg <myon@debian.org> wrote:
Re: Durgamahesh Manne
> with pg_partman By default proc() does not detach tables concurrently.= How
> do we implement tables detach concurrently without blocking other sess= ions
> Here queries not using date column to detach tables with
> run_maintenance_proc() which is not using concurrently=C2=A0 based on = the
> retention policy which leads to scan all available child tables hence = need
> to trigger this proc with concurrently option to avoid blocking other = child
> tables beyond rentention policy while running statements on them

You might have more success by filing pg_partman issues at
https://github.com/pgpartman/pg_partman/issues

> Do we have any other alternative rather than using pg_partman()?

Well you can just run the same commands manually that pg_partman would
run.

Christoph

Hi=C2=A0
You might = have more success by filing pg_partman issues at
ht= tps://github.com/pgpartman/pg_partman/issues=C2=A0 =C2=A0 =C2=A0>>= ;> okay
=C2=A0My intention is to have any other extension=C2=A0other = than pg_partman to manage table partitions manually

Regards
Durga Mahesh
--0000000000000810b9061dceeba4--