Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time
От
Tom Lane
Тема
Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time
Дата
Msg-id
6219.1510539538@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
[GENERAL] Postgres 10.1 fails to start: server did not start in time Adam Brusselback <adambrusselback@gmail.com>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime Christoph Berg <myon@debian.org>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time Adam Brusselback <adambrusselback@gmail.com>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime Christoph Berg <myon@debian.org>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime Christoph Berg <myon@debian.org>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime "Peter J. Holzer" <hjp-pgsql@hjp.at>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime Christoph Berg <myon@debian.org>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime Christoph Berg <myon@debian.org>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime Andres Freund <andres@anarazel.de>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time Adam Brusselback <adambrusselback@gmail.com>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime Joe Conway <mail@joeconway.com>
Andres Freund 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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления