Re: [HACKERS] 64-bit hashjoins

Поиск
Список
Период
Сортировка
От Erik Riedel
Тема Re: [HACKERS] 64-bit hashjoins
Дата
Msg-id 8qyHJry00gNtAmTJAR@andrew.cmu.edu
обсуждение исходный текст
Ответ на Re: [HACKERS] 64-bit hashjoins  (Bruce Momjian <maillist@candle.pha.pa.us>)
Ответы Re: [HACKERS] 64-bit hashjoins  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
> Yes.  If you can tell us the column, by running initdb in debug mode
> (somehow), I think we can figure out the problem.
>  
I changed LONGALIGN to be the "more correct" version, and got the
following trace tidbit from initdb:

<...startup elided...>

+ mkdir /mnt/pgsql/data/base 
+ [ 0 -ne 0 ] 
+ rm -rf /mnt/pgsql/data/base/template1 
+ mkdir /mnt/pgsql/data/base/template1 
+ [ 0 -eq 1 ] 
BACKEND_TALK_ARG=-Q
BACKENDARGS=-boot -C -F -D/mnt/pgsql/data -Q
+ echo Creating template database in /mnt/pgsql/data/base/template1 
Creating template database in /mnt/pgsql/data/base/template1
+ [ 0 -ne 0 ] 
+ postgres -boot -C -F -D/mnt/pgsql/data -Q template1 
+ cat /usr/pdl/lib/pgsql/lib/local1_template1.bki.source 
+ sed -e s/postgres PGUID/er1p 5555/ -e s/PGUID/5555/ 
ERROR:  create index: type for attribute 'attrelid' undefined
ERROR:  create index: type for attribute 'attrelid' undefined
/usr/pdl/lib/pgsql/bin/initdb: 2300 Quit - core dumped
+ [ 131 -ne 0 ] 
+ echo initdb: could not create template database 
initdb: could not create template database
+ [ 0 -eq 0 ] 
+ echo initdb: cleaning up by wiping out /mnt/pgsql/data/base/template1 
initdb: cleaning up by wiping out /mnt/pgsql/data/base/template1
+ rm -rf /mnt/pgsql/data/base/template1 
+ exit 1 

the crash is near the ERROR statements, core dumped.  The dbx
backtrace then shows:

signal Quit at >*[__kill, 0x120185aa8]     beq    r19, 0x120185ac0
(dbx)
(dbx) where
>  0 __kill(0x0, 0x140035d50, 0x12016e508, 0xffffffffffffffff,
0x1400545b8) [0x120185aa8]  1 elog(fmt = 0x1400067b0 = "create index: type for attribute '%s'
undefined") ["elog.c":224, 0x12016e530]  2 NormIndexAttrs(attList = 0x8fc, attNumP = 0x1401e91e2, classOidP =
0x1401e91f8) ["indexcmds.c":500, 0x12007ae5c]  3 DefineIndex(heapRelationName = 0x1401991b0 = "pg_attribute",
indexRelationName = 0x1401c6e00 = "pg_attribute_relid_attnam_index",
accessMethodName = 0x1401e91f8 = "^B", attributeList = 0x1400a48d0,
parameterList = (nil), primary = '^@', predicate = (nil), rangetable =
(nil)) ["indexcmds.c":198, 0x12007a2b4]  4 Int_yyparse()
["/usr0/kosak/tmp/bisontestinstall/share/bison.simple":700, 0x120062c14]  5 BootstrapMain(argv = 0x14007da20)
["bootstrap.c":430,0x1200654c4]  6 main(argv = 0x11ffff5c8) ["main.c":100, 0x1200ae190]
 
(dbx) 

it seems to be ok until it goes to build the indices.

Does this help identify where to look?

Erik





В списке pgsql-hackers по дате отправления:

Предыдущее
От: Erik Riedel
Дата:
Сообщение: Re: [HACKERS] aggregation memory leak and fix
Следующее
От: "Jackson, DeJuan"
Дата:
Сообщение: RE: [HACKERS] backend unstable, \d broken, groups broken was CVS 3-22-99 \d broken?