Re: log_collector doesn't respond to reloads - Mailing list pgsql-bugs

From Tom Lane
Subject Re: log_collector doesn't respond to reloads
Date
Msg-id 18699.1335487841@sss.pgh.pa.us
Whole thread Raw
In response to log_collector doesn't respond to reloads  (Josh Berkus <josh@agliodbs.com>)
Responses Re: log_collector doesn't respond to reloads  (Josh Berkus <josh@agliodbs.com>)
List pgsql-bugs
Josh Berkus <josh@agliodbs.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

pgsql-bugs by date:

Previous
From: Josh Berkus
Date:
Subject: log_collector doesn't respond to reloads
Next
From: Josh Berkus
Date:
Subject: Re: log_collector doesn't respond to reloads