| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6249: Segmentation fault in VirtualXactLock() |
| Date: | 2011-10-11 11:40:11 |
| Message-ID: | CA+TgmobrQAaLA793sQ5n0Q6E4Gau=CSqAK-LQ3wM+_NAUv83qA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Oct 11, 2011 at 3:14 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> 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.
Thanks, committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guimarães | 2011-10-11 13:21:30 | Re: BUG #6204: Using plperl functions generate crash |
| Previous Message | nirodha | 2011-10-11 08:01:25 | BUG #6251: cannot create roles that can actually login |