Re: BUG #13559: WAL replay stuck after DROP VIEW
От | Tom Lane |
---|---|
Тема | Re: BUG #13559: WAL replay stuck after DROP VIEW |
Дата | |
Msg-id | 25767.1439266361@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #13559: WAL replay stuck after DROP VIEW (Maciek Sakrejda <maciek@heroku.com>) |
Ответы |
Re: BUG #13559: WAL replay stuck after DROP VIEW
|
Список | 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 по дате отправления: