Re: pg_repack and locks - Mailing list pgsql-general

From hubert depesz lubaczewski
Subject Re: pg_repack and locks
Date
Msg-id Z4U0OkLb0BYODhIs@depesz.com
Whole thread Raw
In response to pg_repack and locks  (nicolas <nicolas75_fr@yahoo.fr>)
Responses RE: pg_repack and locks
List pgsql-general
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
getthe 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
repackschema. 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




pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Need help in logical replication
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: About PostgreSQL Query Plan