Re: Exception 0xC0000005

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Exception 0xC0000005
Date: 2009-09-25 07:05:02
Message-ID: 4ABC6B9E.8010702@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 25/09/2009 12:45 AM, Grzegorz Jaśkiewicz wrote:
>
>
> On Thu, Sep 24, 2009 at 5:34 PM, Ms swati chande <swativc(at)yahoo(dot)com
> <mailto:swativc(at)yahoo(dot)com>> wrote:
>
> >SIGSEGV in micro$oft world.
> Thanks for your response.
> How can this be resolved?
>
> Just like others said, upgrade to 8.4.1 first.

If you still have the problem once you're running 8.4.1, *then* one of
the options you have is to obtain some more information about how the
crash occurs, though it's not trivial to do so. See:

http://wiki.postgresql.org/index.php?title=Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows

Alternately, and probably more easily, you can produce a self-contained
test case - in this case, probably a .sql file that when run on a newly
created blank database will result in the crash.

--
Craig Ringer

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Oliver Kohll - Mailing Lists 2009-09-25 07:52:55 Re: generic modelling of data models; enforcing constraints dynamically...
Previous Message Peter Eisentraut 2009-09-25 06:29:24 Re: [HACKERS] libpq port number handling