Re: BUG #6249: Segmentation fault in VirtualXactLock()

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: BUG #6249: Segmentation fault in VirtualXactLock()
Дата
Msg-id CA+TgmobrQAaLA793sQ5n0Q6E4Gau=CSqAK-LQ3wM+_NAUv83qA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #6249: Segmentation fault in VirtualXactLock()  (Fujii Masao <masao.fujii@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: BUG #6249: Segmentation fault in VirtualXactLock()
Следующее
От: Guimarães Faria Corcete DUTRA, Leandro
Дата:
Сообщение: Re: BUG #6204: Using plperl functions generate crash