Re: [bug fix] Produce a crash dump before main() on Windows - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject Re: [bug fix] Produce a crash dump before main() on Windows
Date
Msg-id 20190304.132306.90339293.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
In response to Re: [bug fix] Produce a crash dump before main() on Windows  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: [bug fix] Produce a crash dump before main() on Windows
List pgsql-hackers
Hello.

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?

https://docs.microsoft.com/en-us/windows/desktop/wer/collecting-user-mode-dumps

> 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.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rare SSL failures on eelpout
Next
From: Masahiko Sawada
Date:
Subject: Re: reloption to prevent VACUUM from truncating empty pages at theend of relation