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
