Re: BUG #13559: WAL replay stuck after DROP VIEW - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #13559: WAL replay stuck after DROP VIEW
Date
Msg-id 25767.1439266361@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #13559: WAL replay stuck after DROP VIEW  (Maciek Sakrejda <maciek@heroku.com>)
Responses Re: BUG #13559: WAL replay stuck after DROP VIEW  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
Maciek Sakrejda <maciek@heroku.com> writes:
> On Mon, Aug 10, 2015 at 8:18 PM, Michael Paquier <michael.paquier@gmail.com>
> wrote:
>> But this fixed a problem on master where queries got stuck because of
>> the WAL insert lock patch that has been introduced in 9.4 because of a
>> race condition between two backends.

> Interesting, thanks for pointing this out.

FWIW, I doubt that that particular fix is related, because in a replica
server there are no processes performing WAL inserts.

A stack trace of the startup process would definitely be a good thing to
grab if/when you see this again.

And, of course, there is always the standard advice that you ought to
be running current release --- 9.4.4 not 9.4.1.  I do not recognize this
as something we've fixed recently, but that doesn't mean it isn't.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Maciek Sakrejda
Date:
Subject: Re: BUG #13559: WAL replay stuck after DROP VIEW
Next
From: Michael Paquier
Date:
Subject: Re: BUG #13559: WAL replay stuck after DROP VIEW