Re: postgresql-8.3.7 unexpected connection closures

Thanks for the quick response, the log shows the following:

2009-06-19 07:51:47 EST LOG: database system was interrupted; last
known up at 2009-06-18 19:14:37 EST
2009-06-19 07:51:47 EST LOG: database system was not properly shut
down; automatic recovery in progress
2009-06-19 07:51:47 EST LOG: record with zero length at 0/6614E8
2009-06-19 07:51:47 EST LOG: redo is not required
2009-06-19 07:51:47 EST LOG: database system is ready to accept connections
2009-06-19 07:51:47 EST LOG: autovacuum launcher started
2009-06-19 07:54:51 EST LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
2009-06-19 07:54:51 EST LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
2009-06-19 07:54:51 EST LOG: could not receive data from client:
Unknown winsock error 10061
2009-06-19 07:54:52 EST LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
2009-06-19 10:47:35 EST LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487
2009-06-19 10:49:04 EST WARNING: worker took too long to start; cancelled
FATAL: could not reattach to shared memory (key=252, addr=02080000): 487

On Fri, Jun 19, 2009 at 10:40 AM, Craig
Ringer<craig(at)postnewspapers(dot)com(dot)au> wrote:
> On Fri, 2009-06-19 at 09:12 +1000, Andrew Maclean wrote:
>> I posted this a while back but got no useful responses.
>>
>> I have the following 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."
>
> Look at the PostgreSQL server log to see what happened. On Windows, I
> think this is in your  PostgreSQL data directory.
>
> (List members: This seems to confuse Windows admins a lot - they're not
> used to application log files, apparently. Is it worth having the win32
> version of the server report sudden backend death via the Windows event
> logging system, with a reference to the Pg log file? I'm not sure, since
> it's not clear that most Windows admins look at Event Viewer either...)
>
> --
> Craig Ringer
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

--
___________________________________________
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/
___________________________________________