From: | "Aswin J" <jayaswin(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #5682: Postgres Service crashes with exception 0xC0000135 |
Date: | 2010-09-29 07:08:37 |
Message-ID: | 201009290708.o8T78bxW020813@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 5682
Logged by: Aswin J
Email address: jayaswin(at)gmail(dot)com
PostgreSQL version: 8.3.7
Operating system: Windows
Description: Postgres Service crashes with exception 0xC0000135
Details:
I encounter a Postgres crash very frequently on my Windows Box.The postgres
log says
2010-09-27 10:33:30 IST LOG: server process (PID 22656) was terminated by
exception 0xC0000135
2010-09-27 10:33:30 IST HINT: See C include file "ntstatus.h" for a
description of the hexadecimal value.
.
.
2010-09-27 10:33:55 IST FATAL: the database system is in recovery mode
2010-09-27 10:33:55 IST LOG: all server processes terminated;
reinitializing
2010-09-27 10:33:56 IST FATAL: pre-existing shared memory block is still in
use
2010-09-27 10:33:56 IST HINT: Check if there are any old server processes
still running, and terminate them.
Any reason/fix for this?
Thanks,
Aswin
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2010-09-29 08:16:43 | Re: BUG #5682: Postgres Service crashes with exception 0xC0000135 |
Previous Message | Oliver Jowett | 2010-09-29 00:48:11 | Re: [BUGS] Mapping Hibernate boolean to smallint(Postgresql) |