On Fri, May 6, 2011 at 16:08, MauMau <maumau307@gmail.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A06011
> Logged by: =A0 =A0 =A0 =A0 =A0MauMau
> Email address: =A0 =A0 =A0maumau307@gmail.com
> PostgreSQL version: 8.3.12/9.0.3
> Operating system: =A0 Windows XP and Vista
> Description: =A0 =A0 =A0 =A0Some extra messages are output in the event l=
og at
> PostgreSQL startup
> Details:
>
> Hello,
>
> My software package embeds PostgreSQL as a data repository (thank you). T=
he
> PostgreSQL server is registered as a Windows service with "pg_ctl register
> -w ...", and is started as a service with "pg_ctl runservice ...".
>
> The problem is that the following messages are always output in the event
> log at PostgreSQL startup, even when the log_destination parameter doesn't
> contain 'eventlog':
>
> [message 1]
> Waiting for server startup...
>
> [message 2]
> Server started and accepting connections
>
> One of my customers is very sensitive to extra unnecessary messages. They
> gave me a simple and reasonable question "Why are those messages output w=
hen
> event logging is disabled? Is this a bug? Is there a way to prevent these
> messages?"
>
> The expected behavior is that no message is output in the event log when
> log_destination doesn't contain 'eventlog'. I wish the behavior will be
> corrected in 8.3.x.
Any events that happen before we have opened the regular logfile will
be written to the eventlog if the server is running as a Windows
service. There is no way to turn that off (other than removing the
code and recompiling, of course). If we didn't send those to the
eventlog, they would be completely lost since there is no stderr
available to a windows service.
--=20
=A0Magnus Hagander
=A0Me: http://www.hagander.net/
=A0Work: http://www.redpill-linpro.com/