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

From Josh Berkus
Subject Re: log_collector doesn't respond to reloads
Date
Msg-id 4F9ECDFE.2070508@agliodbs.com
Whole thread Raw
In response to Re: log_collector doesn't respond to reloads  (Magnus Hagander <magnus@hagander.net>)
Responses Re: log_collector doesn't respond to reloads  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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

pgsql-bugs by date:

Previous
From: mng5888@gmail.com
Date:
Subject: BUG #6622: ld.so.1: initdb: fatal: libxsit.so.1: open failed: No such file or directory
Next
From: "Kevin Grittner"
Date:
Subject: Re: BUG #6622: ld.so.1: initdb: fatal: libxsit.so.1: open failed: No such file or directory