| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: windows shared memory error |
| Date: | 2009-05-01 15:29:37 |
| Message-ID: | 49FB1561.3060304@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas 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
>
15 seconds beats the hell out of not restarting at all.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-01 15:30:07 | Re: plpgsql's EXIT versus block and loop nesting |
| Previous Message | Tom Lane | 2009-05-01 15:23:24 | Re: Throw some low-level C scutwork at me |