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

From Fujii Masao
Subject Re: BUG #6249: Segmentation fault in VirtualXactLock()
Date
Msg-id CAHGQGwH49YTvLZaoN75Weq+ALMUPn6E-SYE2wwC11RJo6+LxUQ@mail.gmail.com
Whole thread Raw
In response to BUG #6249: Segmentation fault in VirtualXactLock()  ("Fujii Masao" <masao.fujii@gmail.com>)
Responses Re: BUG #6249: Segmentation fault in VirtualXactLock()  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
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.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment

pgsql-bugs by date:

Previous
From: "Fujii Masao"
Date:
Subject: BUG #6249: Segmentation fault in VirtualXactLock()
Next
From: Robert Haas
Date:
Subject: Re: BUG #6249: Segmentation fault in VirtualXactLock()