Collected from the PG bugs email list.
|OS||Windows 7 x64|
|Reported by||Mario Emmenlauer|
Body of first available message related to this bug follows.
The following bug has been logged on the website: Bug reference: 15363 Logged by: Mario Emmenlauer Email address: (redacted) PostgreSQL version: 10.3 Operating system: Windows 7 x64 Description: Dear All, For the past days I've been plagued by a problem where starting postgres.exe failed. The server postgres.exe would just not start, and stdout and stderr where completely empty. Even with debugging mode -d 5 there was absolutely no output. Finally I found the problem (a permission issue about being a privileged user) with the help of a message in the system event log. My question is not about the failed startup, but about the logging. I am confused why the permission problem was logged to Windows system log instead to stdout/stderr? My postgresql.conf is the default from initdb.exe and contains only the default #log_destination = 'stderr'. The documentation at https://www.postgresql.org/docs/current/static/runtime-config-logging.html says "The default is to log to stderr only". I'd like to run postgres.exe in my own watchdog, and it works nicely on Linux and MacOSX. I was relying to see all issues on stdout/stderr. Is it possible to do the same on Windows, to see absolutely all issues on stdout/stderr? Thanks a lot for the very great work, and all the best, Mario Emmenlauer
|2018-09-04 21:30:18+00||=?utf-8?q?PG_Bug_reporting_form?=||BUG #15363: Logging unexpectedly goes to system event log instead of stderr|
|2018-09-04 23:23:08+00||Tom Lane||Re: BUG #15363: Logging unexpectedly goes to system event log instead of stderr|
|2018-09-05 07:46:47+00||Mario Emmenlauer||Re: BUG #15363: Logging unexpectedly goes to system event log instead of stderr|