Re: Postgres 10.1 fails to start: server did not start in time

From: Christoph Berg <myon(at)debian(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, pgsql-general(at)postgresql(dot)org, Adam Brusselback <adambrusselback(at)gmail(dot)com>
Subject: Re: Postgres 10.1 fails to start: server did not start in time
Date: 2017-11-12 19:18:44
Message-ID: 20171112191844.4rry32vdtxzi6crj@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Re: Tom Lane 2017-11-12 <20802(dot)1510513605(at)sss(dot)pgh(dot)pa(dot)us>
> 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.

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.

https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-common.git/tree/systemd/postgresql(at)(dot)service#n18

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

Christoph

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-11-12 19:26:42 Re: Postgres 10.1 fails to start: server did not start in time
Previous Message Karsten Hilbert 2017-11-12 19:13:23 Re: pg on Debian servers