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

From Craig Ringer
Subject Re: BUG #5682: Postgres Service crashes with exception 0xC0000135
Date
Msg-id 4CA32D60.40702@postnewspapers.com.au
Whole thread Raw
In response to BUG #5682: Postgres Service crashes with exception 0xC0000135  ("Aswin J" <jayaswin@gmail.com>)
Responses Re: BUG #5682: Postgres Service crashes with exception 0xC0000135
List pgsql-bugs
On 29/09/2010 5:11 PM, aswin jayaraman wrote:
> 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?

No, it requires a dump and reload. Sorry. You'll want to read the
release notes, as there have been changes between 8.3 and 9.0 that may
affect applications.

http://www.postgresql.org/docs/9/static/release-8-4.html
http://www.postgresql.org/docs/9/static/release-9-0.html

PostgreSQL has seen significant improvements in the Windows port, so
it's worth the update. I unfortunately cannot promise that it'll fix the
issue you're having, though.

--
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: aswin jayaraman
Date:
Subject: Re: BUG #5682: Postgres Service crashes with exception 0xC0000135