| 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:10:11 |
| Message-ID: | 49FB10D3.1040908@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2009-05-01 15:11:52 | Re: windows shared memory error |
| Previous Message | Heikki Linnakangas | 2009-05-01 15:07:50 | Re: plpgsql's EXIT versus block and loop nesting |