| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6249: Segmentation fault in VirtualXactLock() |
| Date: | 2011-10-11 07:14:18 |
| Message-ID: | CAHGQGwH49YTvLZaoN75Weq+ALMUPn6E-SYE2wwC11RJo6+LxUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Oct 11, 2011 at 10:44 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)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 | Content-Type | Size |
|---|---|---|
| fix_segv_virtualxactlock_v1.patch | text/x-patch | 460 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2011-10-11 07:55:00 | Re: [v9.2] make_greater_string() does not return a string in some cases |
| Previous Message | Fujii Masao | 2011-10-11 01:44:39 | BUG #6249: Segmentation fault in VirtualXactLock() |