From: | Andrea Peri <aperi2007(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Postgres 9.0 crash on win7 |
Date: | 2010-10-02 13:08:18 |
Message-ID: | AANLkTimgXQKhbT4b_kFvpVV-1QJSBUsQtfbhwMGR++zF@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
I'm using usually
Postgres 8.4.4 (32bit) + Postgis 1.5.1 on Windows7 64bit.
Now I try-ing the last
Postgres 9.0 (32bit) + Postgis 1.5.2 on the same machine (win7 64bit).
I experience a
crash of Postgres while it is running a huge load of data.
This is the report of log.
2010-10-01 22:38:55 CEST LOG: last completed transaction was at log time
2010-10-01 22:23:51.389+02
2010-10-01 22:38:56 CEST LOG: autovacuum launcher started
2010-10-01 22:38:56 CEST LOG: database system is ready to accept
connections
2010-10-01 22:44:20 CEST LOG: server process (PID 2540) was terminated by
exception 0xC0000005
2010-10-01 22:44:20 CEST HINT: See C include file "ntstatus.h" for a
description of the hexadecimal value.
2010-10-01 22:44:20 CEST LOG: terminating any other active server processes
2010-10-01 22:44:20 CEST WARNING: terminating connection because of crash
of another server process
2010-10-01 22:44:20 CEST DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2010-10-01 22:44:20 CEST HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2010-10-01 22:44:20 CEST WARNING: terminating connection because of crash
of another server process
2010-10-01 22:44:20 CEST DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2010-10-01 22:44:20 CEST HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2010-10-01 22:44:20 CEST LOG: all server processes terminated;
reinitializing
2010-10-01 22:44:31 CEST FATAL: pre-existing shared memory block is still
in use
2010-10-01 22:44:31 CEST HINT: Check if there are any old server processes
still running, and terminate them.
The tablespace where I load the data is new create from postgres9.0
After seeing this.
I try load the same data load procedure (on the same windows machine) using
the postgres 8.4.4 istance and all terminated without any problem.
The procedure is substantially only a huge list of
string sql like
insert into(....)
executed one by one in many tables and with autocommit.
Andrea Peri.
--
-----------------
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-----------------
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-10-02 14:23:20 | Re: BUG #5689: UPDATE locks index before table resulting in deadlock |
Previous Message | Peter Ajamian | 2010-10-02 12:23:04 | BUG #5689: UPDATE locks index before table resulting in deadlock |