Re: log_collector doesn't respond to reloads

On 27/04/12 13:11, Josh Berkus wrote:
> 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
>

Might be a red herring, but I was able to reproduce this if (and only
if) I forgot to create the new dest directory before doing the reload.
Subsequently creating the directory and reloading did not result in a
file in the new location.

Regards

Mark