Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: pg_repack and locks
From: Boris Zentner <bzm@2bz.de>
In-Reply-To: <000001db6a70$ebb65c80$c3231580$@yahoo.fr>
Date: Sun, 19 Jan 2025 14:50:51 +0100
Cc: depesz@depesz.com, pgsql-general@lists.postgresql.org
Message-Id: <23762638-50B3-4406-8757-6EACE2F97FAA@2bz.de>
References: <000001db6a70$ebb65c80$c3231580$@yahoo.fr>
To: nicolas75_fr@yahoo.fr
Archived-At: <https://www.postgresql.org/message-id/23762638-50B3-4406-8757-6EACE2F97FAA%402bz.de>
Precedence: bulk

Hi there,

I think you can use -T 3600 -D  If you don't want to kill the backends.=20
--
Boris


> Am 19.01.2025 um 13:52 schrieb nicolas75_fr@yahoo.fr:
>=20
> =EF=BB=BFHi
>=20
> Thanks for the help but this will not help, killing other process is not s=
afe
> The good way will be that pg_repack tools include a timeout so, that after=
 expiration delay, he will stop waiting and discard the repack action
>=20
> But thanks again for your proposition.
> Regards,
> Nicolas
>=20
> -----Message d'origine-----
> De : depesz@depesz.com <depesz@depesz.com>
> Envoy=C3=A9 : lundi 13 janvier 2025 16:42
> =C3=80 : nicolas <nicolas75_fr@yahoo.fr>
> Cc : pgsql-general@lists.postgresql.org
> Objet : Re: pg_repack and locks
>=20
>> On Mon, Jan 13, 2025 at 12:40:06PM +0000, nicolas wrote:
>> Hello everyone,
>>=20
>> We are using postgresql v12 and added the pg_repack package
>>=20
>> Since I cannot stop other process, I use the =E2=80=9C--no-kill-backend=E2=
=80=9D and
>> Pg_repack will wait indefinitly until pg_repack get the lock
>>=20
>> I get sometimes a problem of lock:
>>=20
>> sometimes, I get indefinitly this message : =E2=80=9CNOTICE: Waiting for 1=
 transactions to finish. First PID: xxxx=E2=80=9D
>>=20
>> this is a real problem because the database is usd all the time.
>> If I kill the process, a trigger on source table will still exist and  te=
mporary tables and type still exists in the repack schema. The tables are no=
t empty if data has been modified in the source table during the repack.
>>=20
>> If I drop table repack tables, I will loose all data modifications
>> done on source table how can I properly cleanup the database ?
>=20
> Allow it to kill offending backends after some time? For example -T 7200?
>=20
> Best regards,
>=20
> depesz
>=20
>=20
>=20
>=20