| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres 10.1 fails to start: server did not start in time |
| Date: | 2017-11-10 21:01:12 |
| Message-ID: | CAMjNa7c2KnyHE6Zk0C1Sh3FnTw91+jORmwJvz5wrvpz88DuDRQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2017-11-10 21:20:28 | Re: Postgres 10.1 fails to start: server did not start in time |
| Previous Message | Tom Lane | 2017-11-10 20:51:52 | Re: Postgres 10.1 fails to start: server did not start in time |