PostgreSQL abnormally terminating with signal 5 - Mailing list pgsql-general

From Carlos H. Reimer
Subject PostgreSQL abnormally terminating with signal 5
Date
Msg-id PEEPKDFEHHEMKBBFPOOKIEIGEMAA.carlos.reimer@opendb.com.br
Whole thread Raw
List pgsql-general
Hi,
 
I´ve a PostgreSQL 8.0.13 running in a Windows XP Pro 2002 SP2 box that is terminating abnormally with signal code 5 every time I make a simple select in one of our tables.
 
2007-06-04 21:24:12 LOG:  database system was shut down at 2007-06-04 21:23:42 E. South America Standard Time
2007-06-04 21:24:12 LOG:  checkpoint record is at 4/7D7FFC68
2007-06-04 21:24:12 LOG:  redo record is at 4/7D7FFC68; undo record is at 0/0; shutdown TRUE
2007-06-04 21:24:12 LOG:  next transaction ID: 1783448; next OID: 3111310
2007-06-04 21:24:12 LOG:  database system is ready
2007-06-04 21:27:39 LOG:  server process (PID 3512) was terminated by signal 5
2007-06-04 21:27:39 LOG:  terminating any other active server processes
2007-06-04 21:27:39 LOG:  all server processes terminated; reinitializing
2007-06-04 21:27:40 LOG:  database system was interrupted at 2007-06-04 21:24:12 E. South America Standard Time
2007-06-04 21:27:40 LOG:  checkpoint record is at 4/7D7FFC68
2007-06-04 21:27:40 LOG:  redo record is at 4/7D7FFC68; undo record is at 0/0; shutdown TRUE
2007-06-04 21:27:40 LOG:  next transaction ID: 1783448; next OID: 3111310
2007-06-04 21:27:40 LOG:  database system was not properly shut down; automatic recovery in progress
2007-06-04 21:27:40 FATAL:  the database system is starting up
2007-06-04 21:27:40 LOG:  record with zero length at 4/7D7FFCA8
2007-06-04 21:27:40 LOG:  redo is not required
2007-06-04 21:27:40 LOG:  database system is ready
 
 
select version();
 PostgreSQL 8.0.13 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)
 
Is there anything I can do to help solve this problem?
 
Thanks!
 
Reimer

pgsql-general by date:

Previous
From: Klint Gore
Date:
Subject: Re: changing 'mons' in interval?
Next
From: Erwin Brandstetter
Date:
Subject: Re: There can be only one! How to avoid the "highlander-problem".