From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | "Shahbaz A(dot) Tyagi" <shahbaz(dot)tyagi(at)sphere(dot)ae> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Connections Crashing |
Date: | 2009-05-14 06:16:34 |
Message-ID: | 4A0BB742.5000508@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Shahbaz A. Tyagi wrote:
> Hi,
>
> Its not happening in all the machines, its only some machines. I am testing
> on XP 32 bit. Its coming only while running Postgres and accessing the DB.
>
> Strange part is that some machines are getting restarted as soon as it gets
> the error.
You mean the whole machine crashes and restarts? That shouldn't even be
possible.
>> From last some time we have started getting error as message dialog
> showing
>> error 0xC0000142 and after that, connections are crashing.
>
>> LOG: server process (PID 8156) was terminated by exception 0xC0000142
It's probably worth making sure you are logging connections
(log_connections) and are recording the PID in the log-lines
(log_line_prefix).
http://www.postgresql.org/docs/8.3/interactive/runtime-config-logging.html
Presumably this error is occuring when a new connection is made, but it
would be sensible to make sure.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-05-14 06:29:00 | Re: Space for pg_dump |
Previous Message | Shahbaz A. Tyagi | 2009-05-14 05:28:19 | Re: Connections Crashing |