Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)
От | Phil Sorber |
---|---|
Тема | Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) |
Дата | |
Msg-id | CADAkt-hM8-fux8FR3J5ufxV4NtxpO9yk+1H6CNJn_bYO-Wc5GA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)
|
Список | pgsql-hackers |
On Sat, Jan 26, 2013 at 11:53 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote: > 2013/1/26 Phil Sorber <phil@omniti.com>: >> On Sat, Jan 26, 2013 at 4:02 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote: >>> Hello >>> >>> We now haw to solve small puppet issue, because our puppets try to >>> start server too early, when old instance live still. >>> >>> Maybe some new parameter - is_done can be useful. >>> >> >> What about something like: >> pg_isready; while [ $? -ne 2 ]; do sleep 1; pg_isready; done > > it is not enough - server is done in a moment, where can be started > again - or when we can do safe copy of database data directory. > I guess i am not completely understanding the case you are trying to solve. Can you explain a bit further? > Regards > > Pavel > > > >> >> Perhaps with a counter to break out of the loop after some number of attempts. >> >>> Regards >>> >>> Pavel >>>
В списке pgsql-hackers по дате отправления: