Re: TRAP during backend startup

Grant Finnemore <grantf(at)guruhut(dot)co(dot)za> writes:
> After an installation from CVS tip, I start the postmaster with the
> -d(anything) flag. The postmaster starts up normally. I then try to
> connect using psql, and either a TRAP is triggered (not using -A 0)
> or an invalid cache id is found (using -A 0)

The backtrace points the finger at Bruce's recent changes in guc.c:
he is trying to call superuser() before the data is available. Bruce,
please fix or revert.

regards, tom lane

#4 0x2a1010 in ExceptionalCondition (
conditionName=0xc21a0 "!(((bool) ((CurrentUserId) != 0)))",
errorType=0xc2130 "BadState", fileName=0xc20d0 "miscinit.c",
lineNumber=252) at assert.c:46
#5 0x2aac18 in GetUserId () at miscinit.c:252
#6 0x2ad1dc in superuser () at superuser.c:37
#7 0x2afb64 in set_config_option (name=0x0, value=0x7b00dc28 "", context=258,
source=PGC_S_ARGV, isLocal=0, changeVal=1) at guc.c:3026
#8 0x2affb8 in SetConfigOption (name=0x7b00dc48 "",
value=0x6 <Address 0x6 out of bounds>, context=PGC_INTERNAL,
source=2063656604) at guc.c:3195
#9 0x221d20 in PostgresMain (argc=5, argv=0x40050a40,
username=0x40050a00 "postgres") at postgres.c:2271
#10 0x1ee494 in BackendRun (port=0x4005ced0) at postmaster.c:2697
#11 0x1edc74 in BackendStartup (port=0x4005ced0) at postmaster.c:2330
#12 0x1ec3e8 in ServerLoop () at postmaster.c:1167
#13 0x1ebe90 in PostmasterMain (argc=4, argv=0x7b03ab14) at postmaster.c:928
#14 0x1ac368 in main (argc=4, argv=0x7b03ab14) at main.c:257
#15 0xc0065784 in ?? () from /usr/lib/libc.1