Re: Deadlock detected after pg_repack receives SIGINT

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Jiří Hlinka <jiri(dot)hlinka(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Deadlock detected after pg_repack receives SIGINT
Date: 2015-11-05 16:43:42
Message-ID: 1622792935.302608.1446741822403.JavaMail.yahoo@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday, November 5, 2015 12:16 AM, Jiří Hlinka <jiri(dot)hlinka(at)gmail(dot)com> wrote:

> My opinion is, that pg_repack should guarantee a consistent,
> deadlock-free behaviour via proper locking policy

I would be very interesting in seeing a description of what locking
policy would guarantee deadlock-free behavior when run concurrently
with unknown software. If you have a link to a paper on the topic,
that would serve as well as a description here.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gavin Flower 2015-11-05 18:08:50 Re: Recursive Arrays 101
Previous Message Rob Sargent 2015-11-05 15:33:41 Re: Recursive Arrays 101