Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica. - Mailing list pgsql-bugs

From Sergey Burladyan
Subject Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica.
Date
Msg-id CAJ2ymdjso73ZY8jVwoLGnw=Jxusi2JNRM9vH+_ao_HRN_nNoWw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica.  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica.  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
On Wed, Oct 21, 2015 at 5:42 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Maxim, did you get the occasion to test your setup with 9.4.5? It
> seems that your environment is more likely to reproduce this deadlock.

I think I also have this issue, but with 9.2.13, today I see dozens of
waiting requests at standby
(via pgadmin Tools-Server Status). All of it is waiting for PID 48205,
it is startup process:
48205 ?        Ss   6289:29 postgres: startup process   recovering
0000001000024C5E000000DF waiting

and startup process hold AccessExclusiveLock for table:
 'virtualxid' <NULL> <NULL> <NULL> <NULL> '1/1' <NULL> <NULL> <NULL>
<NULL> '1/0' 48205 'ExclusiveLock' t t
'relation' 16444 16993 <NULL> <NULL> '<NULL>' <NULL> <NULL> <NULL>
<NULL> '1/0' 48205 'AccessExclusiveLock' t f

I have 'ALTER tblname RENAME xxx TO yyy' at master, before this lock.

And I am using recovery command, without streaming replication.

PostgreSQL 9.2.13 on x86_64-unknown-linux-gnu, compiled by gcc (Debian
4.7.2-5) 4.7.2, 64-bit

--
Sergey Burladyan

pgsql-bugs by date:

Previous
From: David Gould
Date:
Subject: Re: BUG #13702: pg_dump interprets “=”in a db name incorrectly
Next
From: Felipe Gasper
Date:
Subject: pg_restore WAS Re: BUG #13702: pg_dump interprets “=” in a db name incorrectly