Re: startup time
От | David Parker |
---|---|
Тема | Re: startup time |
Дата | |
Msg-id | 07FDEE0ED7455A48AC42AC2070EDFF7C817FFF@corpsrv2.tazznetworks.com обсуждение исходный текст |
Ответ на | startup time ("David Parker" <dparker@tazznetworks.com>) |
Ответы |
Re: startup time
|
Список | pgsql-general |
Does pg_ctl status return true even if the database is not ready yet to receive requests? We are using pg_ctl status to tell us if the database is up, but I'm wondering if it could return true, but a client could connect and still get the "FATAL: database is starting up" error? - DAP >"David Parker" <dparker@tazznetworks.com> writes: >> The problem we are having is that in a customer installation, the >> startup on the database is taking significantly longer than we have >> ever seen it take before. > >Are we talking seconds, minutes, hours, days? > >> But what I'm curious about is what set of things have to happen >> between startup and the server being ready to accept requests. This >> happens on a fresh install, so I don't *think* it should be >recovery processing. > >If it's not doing recovery then the Postgres time proper >should be no more than a second or so, in my experience. Look >for outside-the-database factors. One possibility is a broken >DNS configuration leading to long delays in trying to resolve >socket addresses and such. I've never seen such a problem >causing a delay over a minute though .... > > regards, tom lane >
В списке pgsql-general по дате отправления: