From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: windows shared memory error |
Date: | 2009-05-01 15:30:07 |
Message-ID: | 49FB157F.10105@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page wrote:
> On Fri, May 1, 2009 at 4:10 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> Dave Page wrote:
>>> On Fri, May 1, 2009 at 12:59 AM, Andrew Dunstan <andrew(at)dunslane(dot)net>
>>> wrote:
>>>> It strikes me that we really need to try reconnecting to the shared
>>>> memory
>>>> here several times, and maybe the backoff need to increase each time. On
>>>> a
>>>> loaded server this cause postgres to fail to restart fairly reliably.
>>> At the risk of sounding predictable, +1. Maybe try 5 times, repeating
>>> at 1, 2, 4 & 8 seconds? Any longer seems like it will be a genuine
>>> failure (so does 8 seconds in fact, but I don't suppose it'll hurt to
>>> try).
>> 1+2+4+8 = 15 seconds
>
> Err, yes. What's your point?
If 8 seconds already seems like it's a genuine failure, then perhaps
retrying at 1, 2 and 4 seconds giving a total delay of 7 seconds is
enough. Maybe you meant that 15 s seems like a genuine failure? Well,
either way, never mind :-)
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-05-01 15:38:45 | Re: Throw some low-level C scutwork at me |
Previous Message | Andrew Dunstan | 2009-05-01 15:29:37 | Re: windows shared memory error |