| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 17:38:06 |
| Message-ID: | 4F9ECDFE.2070508@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>> On the whole though, I think this is an invented problem. We've never
>> heard a complaint from the field about it.
>
> I think process title seems reasonable. We do that for archiver for
> example, to tell you where it's writing, don't we?
Yes, we do.
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.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Jeff Frost | 2012-04-30 16:41:09 | Re: 9.1.3 backends getting stuck in 'startup' |