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

From Josh Berkus
Subject log_collector doesn't respond to reloads
Date
Msg-id 4F99E37E.30904@agliodbs.com
Whole thread Raw
Responses Re: log_collector doesn't respond to reloads  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Summary: despite pg_reload(), log directory, filename and destination
don't change

Version: 9.1.3
Platform: RHEL5, custom compile
Severity: Persistant annoyance

Description:

1) change log_directory in postgresql.conf
2) pg_reload_conf()
3) show log_directory displays the correct new directory
4) logging continues to the old directory

Given the custom compile, I'd chalk this up to wonky platform issues,
except that I've seen this problem on other systems, intermittently.
This particular system has the issue in 100% reproduceable fashion, so
I'd like suggestions on how to get to the bottom of it.

I also tried a sighup to the logger process, with  no effect.


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

pgsql-bugs by date:

Previous
From: Josh Berkus
Date:
Subject: Re: 291 pg_toast_temp schemas?
Next
From: Tom Lane
Date:
Subject: Re: log_collector doesn't respond to reloads