From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig Ringer <ringerc@ringerc.id.au>
cc: raghu ram <raghuchennuru@gmail.com>, pgsql-admin@postgresql.org,
	pgsql-general <pgsql-general@postgresql.org>
Subject: Re: [ADMIN] Streaming Replication Server Crash
In-reply-to: <50862525.5060904@ringerc.id.au>
References: 
 <CALnrrJQ81icyt7EpzPwPuXPK0SbSv4+C8uyA=6Nwqh+mLw2hOw@mail.gmail.com>
	<5084EF7E.5080809@ringerc.id.au> <27094.1350910358@sss.pgh.pa.us>
	<50862525.5060904@ringerc.id.au>
Comments: In-reply-to Craig Ringer <ringerc@ringerc.id.au>
	message dated "Tue, 23 Oct 2012 13:03:33 +0800"
Date: Tue, 23 Oct 2012 01:20:31 -0400
Message-ID: <3067.1350969631@sss.pgh.pa.us>

Craig Ringer <ringerc@ringerc.id.au> writes:
> On 10/22/2012 08:52 PM, Tom Lane wrote:
>> But having said that, are we sure 10 is SIGUSR1 on the OP's platform?
>> AFAIK, that signal number is not at all compatible across different
>> flavors of Unix.  (I see SIGUSR1 is 30 on OS X for instance.)

> Gah. I incorrectly though that POSIX specified signal *numbers*, not
> just names. That does not appear to actually be the case. Thanks.

This isn't the first time I've wondered exactly which signal was meant
in a postmaster child-crash report.  Seems like it might be worth
expending some code on a symbolic translation, instead of just printing
the number.  That'd be easy enough (for common signal names) on Unix,
but has anyone got a suggestion how we might do something useful on
Windows?

			regards, tom lane