backend crash with certain statements/tables

From: Jeff Bohmer <bohmer(at)visionlink(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: backend crash with certain statements/tables
Date: 2004-03-02 16:22:56
Message-ID: p04330103bc6926ccf631@[192.168.1.201]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Reproduced in PG 7.4.1 on ...

OS X Server 10.2.8
OS X 10.2.8
RHL 9 (2.4.20-30.9)

Running any of these statements on my database causes the backend to
crash (example from PG log below):

create temp table foo as select * from server_prefs limit 1;
create table foo as select * from server_prefs limit 1;
create temp table foo as select * from agency_dbs limit 1;
create table foo as select * from agency_dbs limit 1;

All of these statements produce expected results (no crash):

create temp table foo as select * from c_group limit 1;
create table foo as select * from c_group limit 1;
create table foo as select * from server_prefs;
create table foo as select * from agency_dbs;
select * from server_prefs limit 1;
select * from agency_dbs limit 1;

Attached is a file that creates a database and only the server_prefs
table and then reproduces the crash for me on both OS X and Linux
when I run it like:

psql -d template1 -U postgres -f pg_crash

Thanks,
- Jeff

2004-03-01 10:32:24 [471] LOG: connection received: host=[local] port=
2004-03-01 10:32:24 [471] LOG: connection authorized: user=username
database=cos
2004-03-01 10:32:34 [471] LOG: statement: create temp table foo as
select * from server_prefs limit 1;
2004-03-01 10:32:35 [19913] LOG: server process (PID 471) was
terminated by signal 10
2004-03-01 10:32:35 [19913] LOG: terminating any other active server processes
2004-03-01 10:32:35 [429] WARNING: terminating connection because of
crash of another server process
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.
HINT: In a moment you should be able to reconnect to the database
and repeat your command.
2004-03-01 10:32:35 [474] LOG: connection received: host=[local] port=
2004-03-01 10:32:35 [474] FATAL: the database system is in recovery mode
2004-03-01 10:32:35 [19913] LOG: all server processes terminated;
reinitializing
2004-03-01 10:32:35 [475] LOG: database system was interrupted at
2004-03-01 10:27:58 MST
2004-03-01 10:32:35 [475] LOG: checkpoint record is at 5/1350BF6C
2004-03-01 10:32:35 [475] LOG: redo record is at 5/1350BF6C; undo
record is at 0/0; shutdown TRUE
2004-03-01 10:32:35 [475] LOG: next transaction ID: 374025; next OID: 46414656
2004-03-01 10:32:35 [475] LOG: database system was not properly shut
down; automatic recovery in progress
2004-03-01 10:32:35 [475] LOG: redo starts at 5/1350BFAC
2004-03-01 10:32:35 [475] LOG: unexpected pageaddr 5/9570000 in log
file 5, segment 19, offset 5701632
2004-03-01 10:32:35 [475] LOG: redo done at 5/1356EB8C
2004-03-01 10:32:38 [475] LOG: database system is ready

Attachment Content-Type Size
pg_crash.gz application/mac-binhex40 10.6 KB

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-03-02 17:46:11 Re: backend crash with certain statements/tables
Previous Message Richard Huxton 2004-03-02 15:39:40 Re: BUG #1088: Name resolution connecting to a database