Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)
Date
Msg-id CAFj8pRCFePZcGoVL2r=kMPRh58_5aBULEACXtkjHN=ARomU_OA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)  (Phil Sorber <phil@omniti.com>)
Responses Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)
List pgsql-hackers
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.

Regards

Pavel



>
> Perhaps with a counter to break out of the loop after some number of attempts.
>
>> Regards
>>
>> Pavel
>>



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Support for REINDEX CONCURRENTLY
Next
From: Phil Sorber
Date:
Subject: Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)