| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Haribabu Kommi' <kommi(dot)haribabu(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: [bug fix] Produce a crash dump before main() on Windows |
| Date: | 2018-07-18 08:38:38 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1FA53A0B@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Haribabu Kommi [mailto:kommi(dot)haribabu(at)gmail(dot)com]
> May be I can give a try by modifying the source code to get the crash.
Thank you, that would be great if you could come up with a good way!
> My point is, With this patch, in case if the postgres crashses
> before reaching main(), does it generate a popup?
>
> If the answer to the above question is yes, then if the popup is
> not attended by the DBA, I feel the postmaster is not able to
> restart all the processes because it is waiting for the crash process
> to close. Am I Correct?
IIRC, the pop up doesn't appear under Windows service. If you start the database server with pg_ctl start on the command prompt, the pop up will appear, which I think is not bad.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2018-07-18 08:59:02 | Re: Bug in gin insert redo code path during re-compression of empty gin data leaf pages |
| Previous Message | Kyotaro HORIGUCHI | 2018-07-18 08:30:14 | Re: [HACKERS] PATCH: Keep one postmaster monitoring pipe per process |