> >> In some cases it writes to the eventlog instead of stderr.=20
>=20
> > Yes, this is what's happening. Odd though, considering that I have:
> > #log_destination =3D 'stderr'
> > In my out-of-the-box config.
>=20
> pg_ctl doesn't read the config file, though. Probably we=20
> need to make write_stderr aware that it's running in an=20
> interactive program rather than in the postmaster, and never=20
> use the eventlog in this context.
It must sitll use the eventlog when called as a service control process,
otherwise any error output from pg_ctl in that scenario would go to
/dev/null...=20
There is code that attempts to check this, but it's apparantly failing.
//Magnus
