Skip site navigation (1) Skip section navigation (2)

Re: log_collector doesn't respond to reloads

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: log_collector doesn't respond to reloads
Date: 2012-04-27 01:23:30
Message-ID: 19446.1335489810@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> On 4/26/12 5:50 PM, Tom Lane wrote:
>> check the process's signal masks like this:
>> grep ^Sig /proc/NNNN/status
>> where NNNN is the logging collector's PID.  Could we see that?

> SigQ:   0/399360
> SigPnd: 0000000000000000
> SigBlk: 0000000000000000
> SigIgn: 0000000001007806
> SigCgt: 0000000000000201

Hm, I'm not sure what SigQ is, but the other values match what I see for
a logging collector process on my Fedora 16 box ... and that process
responds to SIGHUP just fine.  (I believe the rightmost bit of these
masks corresponds to SIGHUP, so this is saying the process is catching
SIGHUP and not currently blocking it, which is what it should be.)

Do you want to try attaching to the collector with a debugger and seeing
if it ever gets into the "if (got_SIGHUP)" block in SysLoggerMain?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Mark KirkwoodDate: 2012-04-27 01:27:44
Subject: Re: log_collector doesn't respond to reloads
Previous:From: Tom LaneDate: 2012-04-27 01:12:17
Subject: Re: hstore parser incorrectly handles malformed input

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group