Re: porting question: funky uid names? - Mailing list pgsql-hackers

From Mark Bixby
Subject Re: porting question: funky uid names?
Date
Msg-id 3AA954D0.F5DA9579@bixby.org
Whole thread Raw
In response to porting question: funky uid names?  (Mark Bixby <mark@bixby.org>)
List pgsql-hackers

Tom Lane wrote:
> 
> Mark Bixby <mark@bixby.org> writes:
> > I just hacked src/test/regress/run_check.sh to invoke initdb with
> > --show.  The user name/id is behaving "correctly" for an MPE machine:
> 
> > SUPERUSERNAME:  MGR.BIXBY
> > SUPERUSERID:    484
> 
> Okay, so much for that theory.
> 
> Can you set a breakpoint at elog() and provide a stack backtrace so we
> can see where this is happening?  I can't think where else in the code
> might be affected, but obviously the problem is somewhere else...

Here's a stack trace from the native MPE debugger (we don't have gdb support
yet).  I'm assuming that all results after the initdb failure should be
suspect, and that's possibly why pg_log wasn't created.  I haven't tried
troubleshooting the pg_log problem yet until after I resolve the uid names
issue.

=============== Initializing check database instance   ================
DEBUG/iX C.25.06 

DEBUG Intrinsic at: 129.0009d09c ?$START$
$1 ($4b) nmdebug > b elog
added: NM    [1] PROG 129.001ad7d8 elog
$2 ($4b) nmdebug > c
Break at: NM    [1] PROG 129.001ad7d8 elog
$3 ($4b) nmdebug > tr    PC=129.001ad7d8 elog
* 0) SP=41843ef0 RP=129.0018f7a4 pg_atoi+$b4 1) SP=41843ef0 RP=129.00182994 int4in+$14 2) SP=41843e70 RP=129.0018296c
?int4in+$8     export stub: 129.001aed28 $CODE$+$138 3) SP=41843e30 RP=129.001af428 fmgr+$98 4) SP=41843db0
RP=129.000c3354InsertOneValue+$264 5) SP=41843cf0 RP=129.000c05d4 Int_yyparse+$924 6) SP=41843c70 RP=129.00000000
(endof NM stack)
 
$4 ($4b) nmdebug > c
=============== Starting regression postmaster         ================
Regression postmaster is running - PID=125239393 PGPORT=65432
=============== Creating regression database...        ================
NOTICE:  mdopen: couldn't open
/BIXBY/PUB/src/postgresql-7.0.3-mpe/src/test/regr
ess/tmp_check/data/pg_log: No such file or directory
NOTICE:  mdopen: couldn't open
/BIXBY/PUB/src/postgresql-7.0.3-mpe/src/test/regr
ess/tmp_check/data/pg_log: No such file or directory
psql: FATAL 1:  cannot open relation pg_log
createdb: database creation failed
createdb failed
make: *** [runcheck] Error 1
-- 
mark@bixby.org
Remainder of .sig suppressed to conserve scarce California electrons...


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: porting question: funky uid names?
Next
From: "Mikheev, Vadim"
Date:
Subject: RE: AW: AW: AW: WAL does not recover gracefully from ou t-of -dis k-sp ace