Re: bug in SignalSomeChildren

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug in SignalSomeChildren
Date: 2010-12-17 13:08:04
Message-ID: AANLkTinVC+POmU+_7Qj+3oaZF47L8QF2zoFz8DLcKp1O@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 14, 2010 at 10:54 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> I found a bug which always prevents SignalSomeChildren with
> BACKEND_TYPE_WALSND from sending a signal to walsender.
>
> Though currently SignalSomeChildren with BACKEND_TYPE_WALSND
> has not been called anywhere, it's not hard to believe that will
> be called in the future. So we should apply the following change.

I think the attached might be a little tidier. Thoughts?

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

Attachment Content-Type Size
signal-some-children.patch application/octet-stream 932 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-12-17 13:34:32 pgsql: Reset 'ps' display just once when resolving VXID conflicts.
Previous Message Greg Smith 2010-12-17 12:18:07 Re: Unnecessary limit on max_standby_streaming_delay