Re: BUG #5682: Postgres Service crashes with exception 0xC0000135 - Mailing list pgsql-bugs

From aswin jayaraman
Subject Re: BUG #5682: Postgres Service crashes with exception 0xC0000135
Date
Msg-id AANLkTik5VG-u-zBdSPJFUNgUo0OfXydtj+JzCRnDsTsP@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5682: Postgres Service crashes with exception 0xC0000135  (Craig Ringer <craig@postnewspapers.com.au>)
List 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,
Aswin

On Wed, Sep 29, 2010 at 2:15 PM, Craig Ringer
<craig@postnewspapers.com.au>wrote:

> 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 http://soapyfrogs.blogspot.com/
>

pgsql-bugs by date:

Previous
From: Craig Ringer
Date:
Subject: Re: BUG #5682: Postgres Service crashes with exception 0xC0000135
Next
From: ""
Date:
Subject: BUG #5683: Service path incorrectly configured