Hello,
I made some further investigations. It seems that my problem was related with my new server hostname. He was named ctrl_cochise which does not conform to standards. After renaming to ctrlcochise I have not been able to reproduce my problems. Something strange is that I was not able to reproduce the problem with autovacuum turned off. While when autovacuum was on, autocvacuum produced errors and sometimes my scripts crashed too with "could not reattach to shared memory (key=288, addr=01FF0000): 487" error too. I keep my server under heavy check for some days and if everything goes fine il will consider this problem as closed. Thanks. Cordialement, Ghislain ROUVIGNAC g...@sylob.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:supp...@sylob.com Entreprise certifiée ISO 9001 version 2000 par le BVQI. -----Message d'origine----- De : Alvaro Herrera [mailto:alvhe...@commandprompt.com] Envoyé : mercredi 1 avril 2009 14:05 À : grouvi Cc : pgsql-bugs@postgresql.org Objet : Re: [BUGS] BUG #4744: Windows 2008: FATAL: could not reattach to shared memory: 487 grouvi wrote: > I have the following messages in logs. > > 2009-04-01 07:01:05 CEST Tx[0] cmd[] PID[2224] DB[] WARNING: worker took > too long to start; cancelled > FATAL: could not reattach to shared memory (key=288, addr=01FF0000): 487 "worker took too long" is an autovacuum launcher message. It's saying that it tried to start a worker, but it never did. If the FATAL message is occuring earlier than the other one, it's possible that it's the worker failing to start. (Note that if there's a lot of work for autovac to do, it will try to start a new worker as soon as it detects that the old one has failed to start. So it's quite likely that you'd see the WARNING first immediately followed by the FATAL message. In fact I'd expect exactly this behavior -- this pair of messages showing up fairly regularly, perhaps almost exactly every autovacuum_naptime seconds.) As for the actual problem, "could not reattach to shared memory", that's a Windows problem that has been reported before, and there has been some investigation about it and how to fix it, but nothing conclusive has been found as far as I know. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
