Skip site navigation (1) Skip section navigation (2)

BUG #3763: crash after create table with primary key defined

From: "migo" <admin(at)abp(dot)pl>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3763: crash after create table with primary key defined
Date: 2007-11-20 10:12:49
Message-ID: 200711201012.lAKACnsR072092@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      3763
Logged by:          migo
Email address:      admin(at)abp(dot)pl
PostgreSQL version: 8.2.4
Operating system:   Gentoo
Description:        crash after create table with primary key defined
Details: 

On psql console:

=>  CREATE TABLE phpbb_acl_roles_data ( role_id INT4 DEFAULT '0' NOT NULL
CHECK (role_id >= 0), auth_option_id INT4 DEFAULT '0' NOT NULL CHECK
(auth_option_id >= 0), auth_setting INT2 DEFAULT '0' NOT NULL, PRIMARY KEY
(role_id, auth_option_id) );
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
wolni=>


In logs after this:
Nov 20 11:02:04 www postgres[32757]: [4-1] wolni>NOTICE:  CREATE TABLE /
PRIMARY KEY will create implicit index "phpbb_acl_roles_data_pkey" for
table
Nov 20 11:02:04 www postgres[32757]: [4-2]  "phpbb_acl_roles_data"
Nov 20 11:02:04 www postgres[32758]: [2-1] [unknown]>LOG:  connection
received: host=[local]
Nov 20 11:02:04 www postgres[32758]: [3-1] wolni>LOG:  connection
authorized: user=wolni database=wolni
Nov 20 11:02:04 www postgres[32731]: [2-1] >LOG:  server process (PID 32757)
was terminated by signal 11
Nov 20 11:02:04 www postgres[32731]: [3-1] >LOG:  terminating any other
active server processes
Nov 20 11:02:04 www postgres[32758]: [4-1] wolni>WARNING:  terminating
connection because of crash of another server process
Nov 20 11:02:04 www postgres[32758]: [4-2] wolni>DETAIL:  The postmaster has
commanded this server process to roll back the current transaction and exit,
because another
Nov 20 11:02:04 www postgres[32758]: [4-3]  server process exited abnormally
and possibly corrupted shared memory.
Nov 20 11:02:04 www postgres[32758]: [4-4] wolni>HINT:  In a moment you
should be able to reconnect to the database and repeat your command.
Nov 20 11:02:04 www postgres[32731]: [4-1] >LOG:  all server processes
terminated; reinitializing
Nov 20 11:02:04 www postgres[32759]: [5-1] >LOG:  database system was
interrupted at 2007-11-20 11:01:46 CET
Nov 20 11:02:04 www postgres[32759]: [6-1] >LOG:  checkpoint record is at
0/F5FBD7FC
Nov 20 11:02:04 www postgres[32759]: [7-1] >LOG:  redo record is at
0/F5FBD7FC; undo record is at 0/0; shutdown TRUE
Nov 20 11:02:04 www postgres[32759]: [8-1] >LOG:  next transaction ID:
0/2321145; next OID: 206248
Nov 20 11:02:04 www postgres[32759]: [9-1] >LOG:  next MultiXactId: 1; next
MultiXactOffset: 0
Nov 20 11:02:04 www postgres[32759]: [10-1] >LOG:  database system was not
properly shut down; automatic recovery in progress
Nov 20 11:02:04 www postgres[32759]: [11-1] >LOG:  redo starts at
0/F5FBD844
Nov 20 11:02:04 www postgres[32759]: [12-1] >LOG:  unexpected pageaddr
0/F0FD4000 in log file 0, segment 245, offset 16596992
Nov 20 11:02:04 www postgres[32759]: [13-1] >LOG:  redo done at 0/F5FD3194
Nov 20 11:02:05 www postgres[32759]: [14-1] >LOG:  database system is ready


What's wrong?

Responses

pgsql-bugs by date

Next:From: Simon RiggsDate: 2007-11-20 11:12:34
Subject: Re: BUG #3763: crash after create table with primary keydefined
Previous:From: Simon RiggsDate: 2007-11-20 08:24:50
Subject: Re: BUG #3760: Comment on restore database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group