Обсуждение: Exception 0xC0000005

On Thu, Sep 24, 2009 at 12:22 PM, Ms swati chande <swativc@yahoo.com> wrote:
>
> Sorry for resending, it got stalled.
> Have subscribed to pgsql-general now.
>
> >What query, exactly?  Which PG version is this?
> >            regards, tom lane
> Its a query involving 15 relations, processing not more than 500 records. The query is written in a .sql file and the
fileis executed as 
>
> \i initq.sql
>
> Infact, know no .sql file is getting executed. All my .sqls have >=15 records.
>
> The error message is:
> psql: initq.sql:64: server closed the connection unexpectedly
>             This probably means the server terminated abnormally
>             before or while processing the request.
> psql: initq.sql:64: connection to server was lost
>
> and the logfile shows:
>
>
> LOG:  server process (PID 3304) was terminated by exception 0xC0000005
>
> HINT:  See C include file "ntstatus.h" for a description of the hexadecimal value.
>
> LOG:  terminating any other active server processes
>
> LOG:  all server processes terminated; reinitializing
>
> LOG:  database system was interrupted; last known up at 2009-09-24 18:01:00 IST
>
> LOG:  database system was not properly shut down; automatic recovery in progress
>
> LOG:  record with zero length at 0/1A71AE0
>
> LOG:  redo is not required
>
> LOG:  database system is ready to accept connections
>
> LOG:  autovacuum launcher started
>
>
>
> The execution for this and other queries has been fine so far.
>
> What is exception 0xC0000005?
>
> I am working on Windows XP.
>
> Have built version 8.4.0 from source using Visual Studio 2005.

1. try upgrading to  8.4.1.  There was at least one known crash
(involving aggregate functions) that was fixed in 8.4.0

2. if that doesn't help, try and reduce your .sql file to a test case
and send it along.

merlin

On 25/09/2009 12:45 AM, Grzegorz Jaśkiewicz wrote:
>
>
> On Thu, Sep 24, 2009 at 5:34 PM, Ms swati chande <swativc@yahoo.com
> <mailto:swativc@yahoo.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