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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: aswin jayaraman <jayaswin(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5682: Postgres Service crashes with exception 0xC0000135
Date: 2010-10-14 22:46:09
Message-ID: 201010142246.o9EMk9w13945@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Craig Ringer wrote:
> 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.

pg_upgrade works for upgrades from 8.3 to 9.0.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Vince 2010-10-15 04:58:23 BUG #5711: input out of error with haversine formual
Previous Message Bruce Momjian 2010-10-14 18:34:54 Re: BUG #5650: Postgres service showing as stopped when in fact it is running