From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: log_collector doesn't respond to reloads |
Date: | 2012-04-30 18:28:06 |
Message-ID: | 21095.1335810486@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> This isn't an invented problem; a brief canvass on IRC shows that people
> run into issues with log_collector reloads fairly commonly. However,
> it's pretty low priority, certainly -- never rises above the level of
> "annoyance". The sort of thing where it would be good to have a
> bugtracker to put it in so the next time someone is working on the log
> collector for other reasons they can tweak this too, or when some new
> hacker wants an easy first patch.
We have that; it's called TODO.
http://wiki.postgresql.org/wiki/Todo
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Matteo Beccati | 2012-05-01 08:50:04 | Re: Errors on CREATE TABLE IF NOT EXISTS |
Previous Message | Kevin Grittner | 2012-04-30 18:08:25 | Re: BUG #6622: ld.so.1: initdb: fatal: libxsit.so.1: open failed: No such file or directory |