On Fri, Mar 12, 2004 at 15:19:29 -0500, Fernando Nasser <[EMAIL PROTECTED]> wrote:
Bruno Wolff III wrote:
I can see their problem with making a dependency to all of apache or including
multilog in their distribution. But they probably could include something
that is only a logger either using some project that is only a logger or
splitting out the logger that is bundled with apache. Then it wouldn't
be unreasonable to make a dependency for postgres requiring that logging
rpm. Other services could also make use of this logging package as well.
Yes that would be nice. I have no idea how difficult it would be to extricate the logrotate program from Apache. I also don't know if there would be any license restrictions, would we be able to redistribute it as an independently package? I don't know the answer.
I was suggesting this as something a distro maintainer (such as Redhat) could do. I think that the postgres developers shouldn't be spending time doing this. They should be just suggesting some possibilities in the admin part of the documentation.
The distro maintainers should only pack proven solutions created by the community. When they add man power to a project they must do it in the community process, not in house.
A decent logging mechanism (that allows log rotation) is important to postgres and should not require one to depend on a distro. They should be able to get it from pgsql land.
It would be nice if there was a community recommended and community tested logging solution, even if the instructions to set it up required one to download and install some apache package.
But adding prodution quality logging to PostgreSQL is still a postgresql community TODO and should not be delegated to the distros and thus restricted to a distro only.
Regards, Fernando
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
