From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: stats collector dies in current |
Date: | 2004-08-15 03:54:49 |
Message-ID: | 411EDE89.2070702@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/14/2004 11:38 PM, Tom Lane wrote:
> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> I see stats collector processes die in current when I suspend
>> postmaster then put it in background from a terminal:
>
>> Is this normal?
>
> Doesn't 7.4 behave the same?
>
> It looks to me like 7.4 and current have the same signal handling.
> I'm not sure why a tstp/cont sequence would create a problem on
> your platform (which is what, btw?) but it ought to cause the same
> problem in 7.4 ...
In that context, is SIGTSTP similar to SIGSTOP in that it cannot be
caught or ignored?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-15 04:19:08 | Re: stats collector dies in current |
Previous Message | Christopher Kings-Lynne | 2004-08-15 03:53:08 | Re: 7.4 backpatches |