Re: log_collector doesn't respond to reloads
От | Josh Berkus |
---|---|
Тема | Re: log_collector doesn't respond to reloads |
Дата | |
Msg-id | 4F99F24A.3030507@agliodbs.com обсуждение исходный текст |
Ответ на | Re: log_collector doesn't respond to reloads (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: log_collector doesn't respond to reloads
Re: log_collector doesn't respond to reloads |
Список | pgsql-bugs |
On 4/26/12 5:50 PM, Tom Lane wrote: > 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? SigQ: 0/399360 SigPnd: 0000000000000000 SigBlk: 0000000000000000 SigIgn: 0000000001007806 SigCgt: 0000000000000201 -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
В списке pgsql-bugs по дате отправления: