| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
| Cc: | raghu ram <raghuchennuru(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [ADMIN] Streaming Replication Server Crash |
| Date: | 2012-10-23 05:20:31 |
| Message-ID: | 3067.1350969631@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Craig Ringer <ringerc(at)ringerc(dot)id(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2012-10-23 05:58:15 | Re: [ADMIN] Streaming Replication Server Crash |
| Previous Message | Craig Ringer | 2012-10-23 05:15:57 | Re: Error on pg_dumpall |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2012-10-23 05:58:15 | Re: [ADMIN] Streaming Replication Server Crash |
| Previous Message | Craig Ringer | 2012-10-23 05:08:10 | Re: Streaming Replication Server Crash |