Stefan Kaltenbrunner wrote:
> Seneca Cunningham wrote:
>
>>On an powerPC AIX 5.3 box, initdb from 8.1beta4 segfaults at
>>src/backend/utils/hash/dynahash.c:673. No segfaults occur and all 98
>>regression tests pass if a test is added to see if keycopy is memcpy and
>>if it is, go through a loop memcpying one byte at a time instead of
>>memcpying everything at once.
>
>
> looks like I'm seeing a similiar problem(using -HEAD) on AIX 5.3ML3
> using the IBM AIX c-compiler. initdb just hangs after "selecting default
> max_connections ..." in a 100% CPU-loop.
yeah this seems to be the very same issue. A backtrace of a stuck
initdb-process looks like:
(gdb) bt
#0 0x10006f10 in bcopy ()
#1 0x1001d398 in hash_search (hashp=0x1001d85c, keyPtr=0xf020f9fc,
action=804399456, foundPtr=0x20029d78 "")
at dynahash.c:673
#2 0x100a5e58 in formrdesc (relationName=0x2006bf38 "t\emplat\e1",
relationReltype=0, hasoids=0 '\0', natts=0,
att=0x200100f8) at relcache.c:1295
#3 0x100a818c in RelationCacheInitialize () at relcache.c:2160
#4 0x102016ec in InitPostgres (dbname=0xd025b7f0 "\200A", username=0x2
"") at postinit.c:424
#5 0x102009e8 in BootstrapMain (argc=271528, argv=0xb0002) at
bootstrap.c:445
#6 0x10000578 in main (argc=0, argv=0x0) at main.c:285
#7 0x1000022c in __start ()
Stefan
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
