Deadlock detected after pg_repack receives SIGINT

From: Jiří Hlinka <jiri(dot)hlinka(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Cc: Jiří Hlinka <jiri(dot)hlinka(at)gmail(dot)com>
Subject: Deadlock detected after pg_repack receives SIGINT
Date: 2015-11-03 12:51:09
Message-ID: CADCCO5rieH8N5itoGB+QyaNW+wmyLDQKvx6PvQs0rjJHwfU_+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'm running a pg_repack from a bash script with timeout of 10 minutes like
so (simplified version):
timeout -s SIGINT 10m pg_repack --table=frequently_updated_table

After the 10 min timeout, the OS sends SIGINT to pg_repack process so the
pg_repack calls:
SELECT repack.repack_drop($1, $2)
and it causes a deadlock with other process which is INSERTing into
frequently_updated_table that has a pg_repack's trigger to log every change
to a repack.log_[OID of frequently_updated_table].

Is it a bug of pg_repack or am I doing something wrong? Should I add some
detailed info?

Thank You for any help,
Jiri

PS: I was trying a mailing list of pg_repack
(http://lists.pgfoundry.org/pipermail/reorg-genera) and github without
any notice. If there is better place to ask, tell me, please.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2015-11-03 13:44:07 Re: Deadlock detected after pg_repack receives SIGINT
Previous Message Victor Blomqvist 2015-11-03 06:10:16 Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type: