| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Jimmy <jimmyjack(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_isready features |
| Date: | 2016-06-15 16:52:25 |
| Message-ID: | 576187C9.5020806@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/15/2016 09:30 AM, David G. Johnston wrote:
> On Wed, Jun 15, 2016 at 12:09 PM, Jimmy <jimmyjack(at)gmail(dot)com
>
> *2. retry*
> This is something I can do via unix script, but ideally it would be
> nice if there would be retry mechanism. For example if I say
> retry=30 then pg_isready would try 30x with x seconds pause in
> between and fail only after 30 retries. This could use default
> retry=0 (current behavior)
>
>
> And the value of this instead of setting a timeout 30x higher is?
Simplicity.
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Imre Samu | 2016-06-15 16:53:03 | Re: pg_isready features |
| Previous Message | Jimmy | 2016-06-15 16:40:12 | Re: pg_isready features |