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 21519.1510514802@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  (Andres Freund <andres@anarazel.de>)
List pgsql-general
Christoph Berg <myon@debian.org> writes:
> The default systemd timeout seems to be 90s. I have already changed
> the systemd timeout to infinity (start) and 1h (stop), so only the
> default pg_ctl timeout remains (60s), which I'd rather not override
> unilaterally.

> That said, isn't 60s way too small for shutting down larger clusters?
> And likewise for starting?

Well, that's tied into the fact that pg_ctl doesn't disturb the server's
state if it gives up waiting.  If it did, we would certainly use a larger
timeout or none at all.  I don't feel a big need to change that default,
but if you have a surrounding script that is going to take adverse action
after a timeout then you need to use a larger value ...
        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: rob stone
Date:
Subject: Re: [GENERAL] pg on Debian servers