Re: bug in SignalSomeChildren - Mailing list pgsql-hackers

From Tom Lane
Subject Re: bug in SignalSomeChildren
Date
Msg-id 696.1292602715@sss.pgh.pa.us
Whole thread Raw
In response to Re: bug in SignalSomeChildren  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: bug in SignalSomeChildren  (Robert Haas <robertmhaas@gmail.com>)
Re: bug in SignalSomeChildren  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Is it possible to save the "is walsender" flag in the Backend struct?
> That would make it possible to solve the problem very easily.

Yeah, I was wondering about that too, but the problem is that the
postmaster doesn't know that at the time it forks the child.  The
flag in shared memory will get set later, but it's hard to tell
how much later.

Of course, that observation also means that anyplace the postmaster
tries to distinguish walsenders from other children is fundamentally
broken anyhow: a walsender that hasn't set the flag yet will get
treated like a regular backend.

I think what we ought to be looking to do is get rid of the distinction,
so that the postmaster treats walsenders the same as other children.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Reset 'ps' display just once when resolving VXID conflicts.
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Reset 'ps' display just once when resolving VXID conflicts.