From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig Ringer <ringerc@ringerc.id.au>
Cc: raghu ram <raghuchennuru@gmail.com>
Cc: pgsql-admin@postgresql.org, pgsql-general <pgsql-general@postgresql.org>
Subject: Re: [ADMIN] Streaming Replication Server Crash
Date: Tue, 23 Oct 2012 01:20:31 -0400
Message-ID: <3067.1350969631@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ringerc@ringerc.id.au, raghuchennuru@gmail.com, pgsql-general@postgresql.org
Subject: Re: [ADMIN] Streaming Replication Server Crash
In-Reply-To: <3067.1350969631@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox