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 00:50:41
Message-ID: 18699.1335487841@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
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?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Josh BerkusDate: 2012-04-27 01:11:38
Subject: Re: log_collector doesn't respond to reloads
Previous:From: Josh BerkusDate: 2012-04-27 00:08:30
Subject: log_collector doesn't respond to reloads

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