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

Re: log_collector doesn't respond to reloads

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: log_collector doesn't respond to reloads
Date: 2012-04-27 01:11:38
Message-ID: 4F99F24A.3030507@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On 4/26/12 5:50 PM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Summary: despite pg_reload(), log directory, filename and destination
>> don't change
> 
> Looking at the code, it's really hard to see how this could possibly
> happen, unless maybe the process is blocking receipt of SIGHUP.  Which
> it shouldn't be.  Not sure about RHEL5, but on recent Linuxen you can
> 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

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

pgsql-bugs by date

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

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