Thread: any idea regarding this error?

any idea regarding this error?

From
"Mel Jamero"
Date:
TIA:

PostgreSQL 7.2; OS Red Hat Linux release 7.3 (Valhalla); 2016 MB Memory;
15% Disk Space Usage

description: an insert into a table fires a trigger that creates other
tables.  same script works in 7.1 & 7.3;

LOGS:

NOTICE:  CREATE TABLE / UNIQUE will create implicit index
'dc_ls_isay_igreet_id_key' for table 'dc_ls_isay_igreet'
NOTICE:  CREATE TABLE will create implicit sequence
'mt_ls_isay_igreet_id_seq' for SERIAL column 'mt_ls_isay_igreet.id'
NOTICE:  CREATE TABLE / UNIQUE will create implicit index
'mt_ls_isay_igreet_id_key' for table 'mt_ls_isay_igreet'
NOTICE:  CREATE TABLE will create implicit sequence
'cm_ls_igreet_message_id_seq' for SERIAL column 'cm_ls_igreet_message.id'
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
'cm_ls_igreet_message_pkey' for table 'cm_ls_igreet_message'
NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY
check(s)
NOTICE:  CREATE TABLE will create implicit sequence
'tb_ls_isay_igreet_id_seq' for SERIAL column 'tb_ls_isay_igreet.id'
NOTICE:  CREATE TABLE / UNIQUE will create implicit index
'tb_ls_isay_igreet_id_key' for table 'tb_ls_isay_igreet'
DEBUG:  server process (pid 5203) was terminated by signal 11
DEBUG:  terminating any other active server processes
DEBUG:  all server processes terminated; reinitializing shared memory and
semaphores
DEBUG:  database system was interrupted at 2003-07-29 17:42:21 PHT
DEBUG:  checkpoint record is at 0/33EA050
DEBUG:  redo record is at 0/33EA050; undo record is at 0/0; shutdown TRUE
DEBUG:  next transaction id: 1425; next oid: 740388
DEBUG:  database system was not properly shut down; automatic recovery in
progress
DEBUG:  redo starts at 0/33EA090
FATAL 1:  The database system is starting up
DEBUG:  ReadRecord: invalid magic number 0000 in log file 0, segment 3,
offset 4440064
DEBUG:  redo done at 0/343BFA8
DEBUG:  database system is ready

PSQL:

mel=# insert into rs_keyword (keyword,pretty_name,
description,service_type_id, service_start, service_end) values
mel-# ('igreet','Greetings','Greeting Service',1,now(),'2003-08-01');
NOTICE:  CREATE TABLE will create implicit sequence
'dc_ls_isay_igreet_id_seq' for SERIAL column 'dc_ls_isay_igreet.id'
NOTICE:  CREATE TABLE / UNIQUE will create implicit index
'dc_ls_isay_igreet_id_key' for table 'dc_ls_isay_igreet'
NOTICE:  CREATE TABLE will create implicit sequence
'mt_ls_isay_igreet_id_seq' for SERIAL column 'mt_ls_isay_igreet.id'
NOTICE:  CREATE TABLE / UNIQUE will create implicit index
'mt_ls_isay_igreet_id_key' for table 'mt_ls_isay_igreet'
NOTICE:  CREATE TABLE will create implicit sequence
'cm_ls_igreet_message_id_seq' for SERIAL column 'cm_ls_igreet_message.id'
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
'cm_ls_igreet_message_pkey' for table 'cm_ls_igreet_message'
NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY
check(s)
NOTICE:  CREATE TABLE will create implicit sequence
'tb_ls_isay_igreet_id_seq' for SERIAL column 'tb_ls_isay_igreet.id'
NOTICE:  CREATE TABLE / UNIQUE will create implicit index
'tb_ls_isay_igreet_id_key' for table 'tb_ls_isay_igreet'
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: Failed.
!#

Regards,

Mel Jamero


Re: any idea regarding this error?

From
Tom Lane
Date:
"Mel Jamero" <mel@gmanmi.tv> writes:
> PostgreSQL 7.2; OS Red Hat Linux release 7.3 (Valhalla); 2016 MB Memory;
> 15% Disk Space Usage
> description: an insert into a table fires a trigger that creates other
> tables.  same script works in 7.1 & 7.3;

> DEBUG:  server process (pid 5203) was terminated by signal 11

Well, my short answer would be "use 7.3" ;-)

If you don't like that answer, the next question is did you really mean
7.2, or 7.2.4?  (Any answer other than "it's 7.2.4" is the wrong one ---
there are bad bugs in earlier 7.2.* releases, and you should update
immediately.)

If it is 7.2.4, and you want to investigate the problem, then look for
the core file left by the crashed backend process.  It should be in
$PGDATA/base/YOURDBNUMBER/core.  (If you don't see any core files, you
probably need to restart the postmaster under "ulimit -c unlimited" to
allow core files to be produced in crashes.)  Once you have a core file,
do this:

    gdb /path/to/postgres /path/to/core
    gdb> bt
    gdb> quit

Send along the gdb output and other details of the problem to the
pgsql-bugs list, and we'll take a look ...

            regards, tom lane

Re: any idea regarding this error?

From
"Mel Jamero"
Date:
weird.  as an act of desperation, we reinstalled the same version of
postgres (this time from source and not rpm) in the same box and made it run
in another port.

darn script worked fine in this this time.  we'll take note of the core file
procedure for future reference.

thanks!

mel

-----Original Message-----
From: pgsql-novice-owner@postgresql.org
[mailto:pgsql-novice-owner@postgresql.org]On Behalf Of Tom Lane
Sent: Tuesday, July 29, 2003 10:47 PM
To: mel@gmanmi.tv
Cc: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] any idea regarding this error?


"Mel Jamero" <mel@gmanmi.tv> writes:
> PostgreSQL 7.2; OS Red Hat Linux release 7.3 (Valhalla); 2016 MB Memory;
> 15% Disk Space Usage
> description: an insert into a table fires a trigger that creates other
> tables.  same script works in 7.1 & 7.3;

> DEBUG:  server process (pid 5203) was terminated by signal 11

Well, my short answer would be "use 7.3" ;-)

If you don't like that answer, the next question is did you really mean
7.2, or 7.2.4?  (Any answer other than "it's 7.2.4" is the wrong one ---
there are bad bugs in earlier 7.2.* releases, and you should update
immediately.)

If it is 7.2.4, and you want to investigate the problem, then look for
the core file left by the crashed backend process.  It should be in
$PGDATA/base/YOURDBNUMBER/core.  (If you don't see any core files, you
probably need to restart the postmaster under "ulimit -c unlimited" to
allow core files to be produced in crashes.)  Once you have a core file,
do this:

    gdb /path/to/postgres /path/to/core
    gdb> bt
    gdb> quit

Send along the gdb output and other details of the problem to the
pgsql-bugs list, and we'll take a look ...

            regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster