Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time
Date
Msg-id 20802.1510513605@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime  (Christoph Berg <myon@debian.org>)
Responses Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime
List pgsql-general
Christoph Berg <myon@debian.org> writes:
> Re: Peter J. Holzer 2017-11-12 <20171112173559.m6chmbyf4vz6fu3c@hjp.at>
>> Wouldn't it be better to remove the timeout?

> If you don't want to block, don't depend on the database service. That
> question is independent from the timeout.

Agreed, but I think Peter has a point: why is there a timeout at all,
let alone one as short as 30 seconds?  Since systemd doesn't serialize
service starts unnecessarily, there seems little value in giving up
quickly.  And we know that cases such as crash recovery may take more
than that.
        regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Christoph Berg
Date:
Subject: Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime
Next
From: Karsten Hilbert
Date:
Subject: Re: [GENERAL] pg on Debian servers