Date: Fri, 19 Jul 2024 16:25:47 +0200
From: Christoph Berg <myon@debian.org>
To: Durgamahesh Manne <maheshpostgres9@gmail.com>
Cc: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org
Subject: Re: Fwd: Regarding tables detach concurrently with
 run_maintenance_proc()
Message-ID: <Zpp3axAcU7oC5lrB@msg.df7cb.de>
Mail-Followup-To: Christoph Berg <myon@debian.org>,
	Durgamahesh Manne <maheshpostgres9@gmail.com>,
	pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org
References: <CAJCZkoJHVcz1QA4A-YpaLAjpW+_gB1D=qWShTS_b+5Rp7E=1Ng@mail.gmail.com>
 <CAJCZkoJayD-9Ck0d0OZb0g-ptvCgv49Xwn_kyxLj9be-Z+=y-A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJCZkoJayD-9Ck0d0OZb0g-ptvCgv49Xwn_kyxLj9be-Z+=y-A@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/Zpp3axAcU7oC5lrB%40msg.df7cb.de>
Precedence: bulk

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