At Tue, 6 Nov 2018 15:53:37 +1100, Haribabu Kommi <kommi.haribabu@gmail.com> wrote in <CAJrrPGcxZi4Z_SttnuUvYOaw+SAdk7+cJgYpuf7ao43vuJLH2w@mail.gmail.com> > Thanks for confirmation of that PostgreSQL runs as service. > > Based on the following details, we can decide whether this fix is required > or not. > 1. Starting of Postgres server using pg_ctl without service is of > production use or not? > 2. Without this fix, how difficult is the problem to find out that > something is preventing the > server to start? In case if it is easy to find out, may be better to > provide some troubleshoot > guide for windows users can help. > > I am in favor of doc fix if it easy to find the problem instead of assuming > the user usage.
I don't have an idea about which is better behavior, but does this work for you?
No, this option is not generating local dumps for postgresql, but this option is useful to
generate dumps for the applications that don't have a specific WER reporting.
> These dumps are configured and controlled independently of the > rest of the WER infrastructure. You can make use of the local > dump collection even if WER is disabled or if the user cancels > WER reporting. The local dump can be different than the dump sent > to Microsoft.
I found that symantec offers this in the steps for error reporting of its products.
Adding some doc changes for the users to refer what can be the issue windows if the
PostgreSQL server doesn't start and there is no core file available.
