Date: Mon, 13 Jan 2025 12:40:06 +0000 (UTC)
From: nicolas <nicolas75_fr@yahoo.fr>
Reply-To: nicolas75_fr@yahoo.fr
To: pgsql-general@lists.postgresql.org
Message-ID: <1726378815.4209727.1736772006968@mail.yahoo.com>
Subject: pg_repack and locks
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <1726378815.4209727.1736772006968.ref@mail.yahoo.com>
Content-Length: 888
Archived-At: <https://www.postgresql.org/message-id/1726378815.4209727.1736772006968%40mail.yahoo.com>
Precedence: bulk

Hello everyone,=20

We are using postgresql v12 and added the pg_repack package

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

I get sometimes a problem of lock:

sometimes, I get indefinitly this message : =E2=80=9CNOTICE: Waiting for 1 =
transactions to finish. First PID: xxxx=E2=80=9D

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  temp=
orary 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.

If I drop table repack tables, I will loose all data modifications done on =
source table
how can I properly cleanup the database ?

Hope this is clear and that somebody can help

best raegards,
Nicolas