I looked at the log files. The log file for one crash I had looks
like it got to loading data in one of the larger tables. Finished
inserting a record and stopped. It did complain about the fact that
the tables already existed but seemed to continue and loaded about 49
tables before it quit. It didn't give any messages at that point.
This is the start of the log file after I restarted the computer
after a postgres crash:
2009-04-27 18:00:31 PDT LOG: database system was interrupted; last
known up at 2009-04-27 17:45:18 PDT
2009-04-27 18:00:31 PDT LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
2009-04-27 18:00:31 PDT FATAL: the database system is starting up
2009-04-27 18:00:31 PDT LOG: database system was not properly shut
down; automatic recovery in progress
2009-04-27 18:00:31 PDT LOG: record with zero length at 0/268F86E8
2009-04-27 18:00:31 PDT LOG: redo is not required
2009-04-27 18:00:31 PDT LOG: database system is ready to accept connections
2009-04-27 18:00:32 PDT LOG: autovacuum launcher started
This is the start of the log file after I tried to restore the database again:
2009-04-27 18:19:12 PDT LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
2009-04-27 18:19:20 PDT LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
2009-04-27 18:19:44 PDT LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
2009-04-27 18:19:44 PDT ERROR: language "plpgsql" already exists
2009-04-27 18:19:44 PDT STATEMENT:
CREATE PROCEDURAL LANGUAGE plpgsql;
Scott:
I'm really starting to wonder about your hardware and / or OS. Are
you running any anti-virus software (if so turn it off and / or
uninstall it)? Have you tested your machine with something like
memtest86+?
All computers are running NOD32 for anti-virus. All are updated and
running. I haven't run Memtest86 on any of them. This has happened on
5 different computers including my personal laptop which is never
connected to the network at the office.
Christine
At 11:35 AM 28/04/2009, you wrote:
Christine Penner wrote:
> The crashes I get are the windows, this program has encountered a
> problem and must close, error. At that point I can't do anything with
> Postgres. I can't restart the service. I have to restart windows.
The PostgreSQL logs should have more info regarding the crash. I think
you really need to solve this crash; it should normally never happen.
(Postgres can be configured so that the log ends up in the Windows event
log, by setting log_destination=eventlog in postgresql.conf. If you
haven't set that up, it's probably ending up in a file somewhere).
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
