Date: Mon, 13 Jan 2025 16:41:46 +0100
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: nicolas <nicolas75_fr@yahoo.fr>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: pg_repack and locks
Message-ID: <Z4U0OkLb0BYODhIs@depesz.com>
Reply-To: depesz@depesz.com
References: <1726378815.4209727.1736772006968.ref@mail.yahoo.com>
 <1726378815.4209727.1736772006968@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1726378815.4209727.1736772006968@mail.yahoo.com>
Archived-At: <https://www.postgresql.org/message-id/Z4U0OkLb0BYODhIs%40depesz.com>
Precedence: bulk

On Mon, Jan 13, 2025 at 12:40:06PM +0000, nicolas wrote:
> Hello everyone, 
> 
> We are using postgresql v12 and added the pg_repack package
> 
> Since I cannot stop other process, I use the “--no-kill-backend” 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 : “NOTICE: Waiting for 1 transactions to finish. First PID: xxxx”
> 
> 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.
> 
> If I drop table repack tables, I will loose all data modifications 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