From: | "Ghislain ROUVIGNAC" <ghr(at)sylob(dot)com> |
---|---|
To: | "'Bruce Momjian'" <bruce(at)momjian(dot)us> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #4768: FATAL:could not reattach to shared memory:487 |
Date: | 2009-04-22 12:44:39 |
Message-ID: | 000001c9c348$1a144f10$4e3ced30$@com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Stopping and starting does not seem to fix the problem.
I stopped and started my Windows server today.
The problem reappeared the second time I launched my db update scripts.
Cordialement,
Ghislain ROUVIGNAC
ghr(at)sylob(dot)com
Editeur-Intégrateur de solutions ERP
7 rue Marcel Dassault - Z.A. La Mouline - 81990 Cambon d'Albi - FRANCE
Tél : (+33) (0)5 63 53 08 18 - Fax : (+33) (0)5 63 53 07 42 - www.sylob.com
Hot line : (+33) (0)5 63 53 78 35 - mailto:support(at)sylob(dot)com
Entreprise certifiée ISO 9001 version 2000 par le BVQI.
-----Message d'origine-----
De : Bruce Momjian [mailto:bruce(at)momjian(dot)us]
Envoyé : mardi 21 avril 2009 16:53
À : Ghislain ROUVIGNAC
Cc : pgsql-bugs(at)postgresql(dot)org
Objet : Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487
Ghislain ROUVIGNAC wrote:
> I didn't tried to reboot the windows server.
> I'll try it when i will have time.
>
>
> Thank you for the references to the problem.
OK, let us know if it does not fix the problem. As you can see this
bug has been around for a while.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Campbell | 2009-04-22 12:50:26 | Re: Workaround for bug #4608? |
Previous Message | Bruce Momjian | 2009-04-22 12:43:35 | Re: Workaround for bug #4608? |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Campbell | 2009-04-22 12:50:26 | Re: Workaround for bug #4608? |
Previous Message | Bruce Momjian | 2009-04-22 12:43:35 | Re: Workaround for bug #4608? |