| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
| Cc: | pgsql-general(at)postgresql(dot)org, Adam Brusselback <adambrusselback(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Postgres 10.1 fails to start: server did not start in time |
| Date: | 2017-11-12 18:52:34 |
| Message-ID: | 20171112185233.tzynljip2k3ygcxn@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Re: Peter J. Holzer 2017-11-12 <20171112173559(dot)m6chmbyf4vz6fu3c(at)hjp(dot)at>
> Wouldn't it be better to remove the timeout? If some other service
> depends on PostgreSQL it probably shouldn't be startet until PostgreSQL
> is really up and services which don't need PostgreSQL (e.g. SSH or X11
> login or a web- or mail server) shouldn't depend on it.
>
> One of the purported advantages of systemd over SystemV init is that it
> starts up services in parallel, so a service which takes a long (or
> infinite) time to start doesn't block other services.
If you don't want to block, don't depend on the database service. That
question is independent from the timeout.
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-11-12 19:06:45 | Re: Postgres 10.1 fails to start: server did not start in time |
| Previous Message | Peter J. Holzer | 2017-11-12 17:35:59 | Re: Postgres 10.1 fails to start: server did not start in time |