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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Christoph Berg <myon(at)debian(dot)org>, "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-13 02:18:58
Message-ID: 6219.1510539538@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andres Freund <andres(at)anarazel(dot)de> writes:
> we could really do better than just wonder whether our signal to
> shutdown was received or not. There probably should be a quite short
> timeout for the server to change status, and then a much longer one for
> that shutdown to finish.

While I don't want to just raise the timeout, I could get behind a more
thorough rethinking of the behavior there.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2017-11-13 03:48:27 Re: Migrating plattaform
Previous Message Tom Lane 2017-11-13 01:51:01 Re: Multiple unnests in query