| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Michael Paquier' <michael(at)paquier(dot)xyz> |
| Cc: | 'Robert Haas' <robertmhaas(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, 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-23 08:16:52 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1FA55872@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Michael Paquier [mailto:michael(at)paquier(dot)xyz]
> When you use pg_ctl start within the command prompt, then closing the prompt
> session also causes Postgres to stop immediately. Would it be a problem?
No. But that makes me think more of the startup on command prompt as non-production usage.
> Another question I have is that I have seen Postgres fail to start because
> of missing dependent libraries, which happened after the postmaster startup
> as this was reported in the logs, could it be a problem with this patch?
> If the system waits for an operator to close this pop-up window, then it
> becomes harder to check automatically such failures and relies on the test
> application to timeout, if it is wise enough to do, which is not always
> the case..
I guess that is due to some missing files related to the libraries listed in shared_preload_library. If so, no, because this patch relates to failure before main().
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2018-07-23 08:20:13 | Re: [Proposal] Add accumulated statistics for wait event |
| Previous Message | Michael Paquier | 2018-07-23 07:53:15 | Re: [Proposal] Add accumulated statistics for wait event |