Re: postgresql-8.3.7 unexpected connection closures
От | Andrew Maclean |
---|---|
Тема | Re: postgresql-8.3.7 unexpected connection closures |
Дата | |
Msg-id | e7ddbec60906221628q44fdd712ia51e475f2bc04a2e@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: postgresql-8.3.7 unexpected connection closures (Craig Ringer <craig@postnewspapers.com.au>) |
Ответы |
Re: postgresql-8.3.7 unexpected connection closures
Re: postgresql-8.3.7 unexpected connection closures |
Список | pgsql-general |
[snipity snip snip] Notwithstanding all the previous discussion. I still think there is a problem with postgresql on windows. Messages in the log are consistently of the form: 2009-06-23 08:28:26 EST WARNING: worker took too long to start; cancelled FATAL: could not reattach to shared memory (key=252, addr=023F0000): 487 2009-06-23 08:35:58 EST WARNING: worker took too long to start; cancelled FATAL: could not reattach to shared memory (key=252, addr=023F0000): 487 Postgres is actually usable if I restart the service after the machine has booted up. This fixes the problem triggering the error message: "Error connecting to the server: server closed the connection unexpectedly. This probably means that the server terminated abnormally before or while processing the request." However the above messages are still appearing. Personally I have no issues with the installation process. Although I am the first to admit that sometimes I forget to check the log file and the event files. I get used to Linux. Regards Andrew -- ___________________________________________ Andrew J. P. Maclean Centre for Autonomous Systems The Rose Street Building J04 The University of Sydney 2006 NSW AUSTRALIA Ph: +61 2 9351 3283 Fax: +61 2 9351 7474 URL: http://www.acfr.usyd.edu.au/ ___________________________________________
В списке pgsql-general по дате отправления: