Skip site navigation (1) Skip section navigation (2)

Re: BUG #5682: Postgres Service crashes with exception 0xC0000135

From: aswin jayaraman <jayaswin(at)gmail(dot)com>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5682: Postgres Service crashes with exception 0xC0000135
Date: 2010-09-29 09:11:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
I ll try that out.Is there means to do an upgrade to 8.3 to 8.4/9.0 with the
data in place?

Thanks in Advance,

On Wed, Sep 29, 2010 at 2:15 PM, Craig Ringer

> Please reply with "reply all" so that others who're on the -bugs list may
> see and respond to your posts.
> I've CC'd the list. My reply follows below.
> On 29/09/2010 4:32 PM, aswin jayaraman wrote:
>> I am running it on a Windows Vista 32 bit.The crash happens randomly.So
>> the connections we make to the database fail. This though is not seen on
>> all machines but on the ones it is seen it is quite consistent.Should I
>> try postgreSQL 9.0 for better results? Or is there a fix for the issue?
> I haven't personally seen this particular issue reported, though there have
> been plenty of problems with shared memory that seem to have been fixed in
> 8.4 .
> It would be a good idea to try 8.4 or 9.0 and see if you still have the
> problem there. If you do, then we'll at least be working with a current
> version when debugging/testing.
> --
> Craig Ringer
> Tech-related writing at

In response to


pgsql-bugs by date

Next:From: donovanscDate: 2010-09-29 10:16:49
Subject: BUG #5683: Service path incorrectly configured
Previous:From: Craig RingerDate: 2010-09-29 08:45:07
Subject: Re: BUG #5682: Postgres Service crashes with exception 0xC0000135

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group