6.3.1: Core during initdb on SVR4 (MIPS)

With reference to the following mesage...We are wondering what was the resolution for the core..

thanks
gautam

6.3.1: Core during initdb on SVR4 (MIPS)

*    From: Frank Ridderbusch <ridderbusch.pad@sni.de <mailto:ridderbusch.pad@sni.de>>
*    To: pgsql-hackers@postgresql.org <mailto:pgsql-hackers@postgresql.org>
*    Subject: 6.3.1: Core during initdb on SVR4 (MIPS)
*    Date: Thu, 26 Mar 1998 13:46:51 GMT

Hi,

just got me the complete 6.3.1 tarball. Compilation and installation
went smoothly for the most part.

Problem is, that the backend dumps core during the initdb run. Here is
the transscript (see the 'Abort' below, vacuuming template1).

postgres@utensil (9) $ bin/initdb
initdb: using /home/tools/pgsql-6.3/lib/local1_template1.bki.source as input to create the template database.
initdb: using /home/tools/pgsql-6.3/lib/global1.bki.source as input to create the global classes.
initdb: using /home/tools/pgsql-6.3/lib/pg_hba.conf.sample as the host-based authentication control file.

We are initializing the database system with username postgres (uid=121).
This user will own all the files and must also own the server process.

Creating Postgres database system directory /home/tools/pgsql-6.3/data/base

initdb: creating template database in /home/tools/pgsql-6.3/data/base/template1
Running: postgres -boot -C -F -D/home/tools/pgsql-6.3/data -Q template1

Creating global classes in /base
Running: postgres -boot -C -F -D/home/tools/pgsql-6.3/data -Q template1

Adding template1 database to pg_database...
Running: postgres -boot -C -F -D/home/tools/pgsql-6.3/data -Q template1 < /tmp/create.6347

vacuuming template1
Abort
creating public pg_user view
loading pg_description

I then pulled the core into dbx and got the following info.

postgres@utensil (16) $ dbx ../../../bin/postgres core
dbx 2.1A00 SINIX (Apr  6 1995)
Copyright (C) Siemens Nixdorf Informationssysteme AG 1995
Base:    BSD, Copyright (C) The Regents of the University of California
All rights reserved
reading symbolic information ...
Current signal in memory image is: SIGIOT (6) (generated by pid 6409 uid 121)
[using memory image in core]
Type 'help' for help
(dbx) where
.kill() at 0x482d994
.abort() at 0x4822d30
ExcAbort(excP = 0x62ddc0, detail = 0, data = (nilv), message = "!(RelationIsValid(relation))"), line 29 in "excabort.c"
ExcUnCaught(excP = 0x62ddc0, detail = 0, data = (nilv), message = "!(RelationIsValid(relation))"), line 173 in "exc.c"
ExcRaise(excP = 0x62ddc0, detail = 0, data = (nilv), message = "!(RelationIsValid(relation))"), line 190 in "exc.c"
ExceptionalCondition(conditionName = "!(RelationIsValid(relation))", exceptionP = 0x62ddc0, detail = (nilv), fileName =
"indexam.c",lineNumber = 231), line 69 in "assert.c" 
index_beginscan(relation = (nilv), scanFromEnd = '\0', numberOfKeys = 0, key = (nilv)), line 231 in "indexam.c"
vc_scanoneind(indrel = (nilv), nhtups = 0), line 1448 in "vacuum.c"
vc_vacone(relid = 1247, analyze = '\0', va_cols = (nilv)), line 560 in "vacuum.c"
vc_vacuum(VacRelP = (nilv), analyze = '\0', va_cols = (nilv)), line 253 in "vacuum.c"
.vacuum.vacuum(vacrel = (nilv), verbose = '\0', analyze = '\0', va_spec = (nilv)), line 159 in "vacuum.c"
ProcessUtility(parsetree = 0x66c770, dest = Debug), line 633 in "utility.c"
pg_exec_query_dest(query_string = "vacuum\n", argv = (nilv), typev = (nilv), nargs = 0, dest = Debug), line 653 in
"postgres.c"
pg_exec_query(query_string = "vacuum\n", argv = (nilv), typev = (nilv), nargs = 0), line 601 in "postgres.c"
PostgresMain(argc = 7, argv = 0x7fffe7ac), line 1382 in "postgres.c"
.main() at 0x4bb29c
__start() at 0x417de4
(dbx)

MfG/Regards
--    /====                         Siemens Nixdorf Informationssysteme AG   /    Ridderbusch        / ,   Abt.: OEC XS
QM4 /                       /./   Heinz Nixdorf Ring /=== /,== ,===/  /,==,  //    33106 Paderborn, Germany/    //   /
/  //   / / \   Tel.: (49) 5251-8-15211 
/    /     `==/\ /    / /   \ Email: ridderbusch.pad@sni.de

Since I have taken all the Gates out of my computer, it finally works!!