| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Adam Brusselback <adambrusselback(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Christoph Berg <myon(at)debian(dot)org> |
| Subject: | Re: Postgres 10.1 fails to start: server did not start in time |
| Date: | 2017-11-10 21:20:28 |
| Message-ID: | 42b1d9dc-29d6-6408-298b-42b2b77d8666@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/10/2017 01:01 PM, Adam Brusselback wrote:
>> You might want to increase pg_ctl's wait timeout for this situation,
>> since the default's evidently too little. However ...
> Got it, thanks.
>
>> ... pg_ctl itself wouldn't decide to forcibly shut down the server
>> if the timeout expired. It merely stops waiting and tells you so.
>> It seems like this must represent misdesign of whatever start script
>> you're using. I think you need to complain to the Debian packagers
>> about that.
>
> Hmm, interesting. I installed from this repo:
> http://apt.postgresql.org/pub/repos/apt/ stretch-pgdg main
>
> I was assuming someone in the Postgres project was involved in
> packaging it. Do you know who I should reach out to in that case?
I'm pretty sure Christoph Berg is at least involved. I cc'd him here in
case he misses this thread.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-11-10 21:29:17 | Re: Postgres 10.1 fails to start: server did not start in time |
| Previous Message | Adam Brusselback | 2017-11-10 21:01:12 | Re: Postgres 10.1 fails to start: server did not start in time |