From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Maciek Sakrejda <maciek(at)heroku(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #13559: WAL replay stuck after DROP VIEW |
Date: | 2015-08-11 04:12:41 |
Message-ID: | 25767.1439266361@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Maciek Sakrejda <maciek(at)heroku(dot)com> writes:
> On Mon, Aug 10, 2015 at 8:18 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-08-11 04:19:13 | Re: BUG #13559: WAL replay stuck after DROP VIEW |
Previous Message | Maciek Sakrejda | 2015-08-11 04:03:20 | Re: BUG #13559: WAL replay stuck after DROP VIEW |