Re: BUG #6249: Segmentation fault in VirtualXactLock() - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #6249: Segmentation fault in VirtualXactLock()
Date
Msg-id CA+TgmobrQAaLA793sQ5n0Q6E4Gau=CSqAK-LQ3wM+_NAUv83qA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #6249: Segmentation fault in VirtualXactLock()  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-bugs
On Tue, Oct 11, 2011 at 3:14 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Tue, Oct 11, 2011 at 10:44 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> When I built Streaming Replication and Hot Standby environment, set
>> max_standby_streaming_delay to 1s and ran the following shell script which
>> creates the conflict between read-only query and recovery, SEGV occurred on
>> the standby.
>
> In my investigation, the cause is that VirtualXactLock() doesn't
> handle correctly
> the case where BackendIdGetProc() returns NULL when the target backend has
> already ended. Attached patch will fix this issue.

Thanks, committed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Fujii Masao
Date:
Subject: Re: BUG #6249: Segmentation fault in VirtualXactLock()
Next
From: Guimarães Faria Corcete DUTRA, Leandro
Date:
Subject: Re: BUG #6204: Using plperl functions generate crash