From: <nicolas75_fr@yahoo.fr>
To: <depesz@depesz.com>
Cc: <pgsql-general@lists.postgresql.org>
References: <1726378815.4209727.1736772006968.ref@mail.yahoo.com> <1726378815.4209727.1736772006968@mail.yahoo.com> <Z4U0OkLb0BYODhIs@depesz.com>
In-Reply-To: <Z4U0OkLb0BYODhIs@depesz.com>
Subject: RE: pg_repack and locks
Date: Sun, 19 Jan 2025 13:51:53 +0100
Message-ID: <000001db6a70$ebb65c80$c3231580$@yahoo.fr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQMGQEVA7dVrgCJU6kC+ijeZrizzlAFwY4sSAYy4xmGwsHdysA==
Content-Language: fr
Content-Length: 1543
Archived-At: <https://www.postgresql.org/message-id/000001db6a70%24ebb65c80%24c3231580%24%40yahoo.fr>
Precedence: bulk

Hi

Thanks for the help but this will not help, killing other process is not =
safe
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

But thanks again for your proposition.
Regards,
Nicolas

-----Message d'origine-----
De : depesz@depesz.com <depesz@depesz.com>=20
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

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=20
> 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  =
temporary tables and type still exists in the repack schema. The tables =
are not 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=20
> done on source table how can I properly cleanup the database ?

Allow it to kill offending backends after some time? For example -T =
7200?

Best regards,

depesz