Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica.

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica.
Date: 2015-10-24 17:28:17
Message-ID: CAMkU=1yykrRo71Ldf5sKg2eQUJ+m_+WHGnvn_8i5oRO1V9X9mg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Oct 24, 2015 at 4:08 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Sat, Oct 24, 2015 at 4:16 PM, Maxim Boguk wrote:

>> I suppose deadlock had been happened when replay process replaying
>> truncation to zero pages after vacuum on the master db (but it's mostly
>> theory with no good evidence).
>
> By what was AccessExclusiveLock created on master? Did you run
> TRUNCATE on those two relations from time to time?

AccessExclusiveLock is automatically taken by vacuum when it thinks it
can truncate pages off the end of the relation.

Cheers,

Jeff

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Stehule 2015-10-25 03:14:26 Re: BUG #13708: strange behaviour instead of syntax error
Previous Message Greg Stark 2015-10-24 12:04:53 Re: BUG #13708: strange behaviour instead of syntax error