From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | log_collector doesn't respond to reloads |
Date: | 2012-04-27 00:08:30 |
Message-ID: | 4F99E37E.30904@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-04-27 00:50:41 | Re: log_collector doesn't respond to reloads |
Previous Message | Josh Berkus | 2012-04-26 23:54:56 | Re: 291 pg_toast_temp schemas? |