Re: Problem during Windows service start - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: Problem during Windows service start
Date
Msg-id CAKPRHzKxkm_6fQt4eQrfoTKT-FM+aAc9Ykuk54uwxLUWxD74Lw@mail.gmail.com
Whole thread Raw
In response to Problem during Windows service start  ("Sakai, Teppei" <sakai.teppei@jp.fujitsu.com>)
Responses Re: Problem during Windows service start  (Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Sorry in advance for link-breaking message, but the original mail was
too old and gmail doesn't allow me to craft required headers to link
to it.

https://www.postgresql.org/message-id/CAKm4Xs71Ma8bV1fY6Gfz9Mg3AKmiHuoJNpxeDVF_KTVOKoy1WQ%40mail.gmail.com

> Please find the proposed patch for review. I will attach it to
> commitfest as well

Pacemaker suffers the same thing. We suggest our customers that "start
server alone to perform recovery then start pacemaker if it is
expected to take a long time for recovery so that reaches time out".

I don't think it is good think to let status SERVICE_RUNNING although
it actually is not (yet). I think the right direction here is that, if
pg_ctl returns by timeout, pgwin32_ServiceMain kills the starting
server then report something like "timedout and server was stopped,
please make sure the server not to take a long time to perform
recovery.".

Thougts?

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Rushabh Lathia
Date:
Subject: Re: POC: Cleaning up orphaned files using undo logs
Next
From: Michael Paquier
Date:
Subject: Seek failure at end of FSM file during WAL replay (in 11)