Re: BUG #5412: Crash in production SIGSEGV, equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x966508c4) at tupdesc.c
От | Rusty Conover |
---|---|
Тема | Re: BUG #5412: Crash in production SIGSEGV, equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x966508c4) at tupdesc.c |
Дата | |
Msg-id | 4B37EAC6-3455-4ADE-99A4-46A37CD1A866@infogears.com обсуждение исходный текст |
Ответ на | Re: BUG #5412: Crash in production SIGSEGV, equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x966508c4) at tupdesc.c (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: BUG #5412: test case produced, possible race condition.
|
Список | pgsql-bugs |
On Apr 9, 2010, at 2:23 PM, Heikki Linnakangas wrote: > Rusty Conover wrote: >> The bug is reproducible, I'm not sure how to proceed.=20=20 >=20 > How do you reproduce it? Can you make a self-contained test case? >=20 I can reproduce it by running my code, I haven't found a good test case yet= because the bug seems to depend on an interaction between postgres process= es. I have about 12 different db sessions creating temporary tables with the sa= me name them dropping them very quickly in the same database. While other = processes are just running queries in other databases. The process that is= crashing isn't one of the processes that is creating and dropping temporar= y tables, its completely separate in a different database. Here a new crash from today with the same trace: #0 equalTupleDescs (tupdesc1=3D0x7f7f7f7f, tupdesc2=3D0x9661e430) at tupde= sc.c:311 311 if (tupdesc1->natts !=3D tupdesc2->natts) (gdb) bt #0 equalTupleDescs (tupdesc1=3D0x7f7f7f7f, tupdesc2=3D0x9661e430) at tupde= sc.c:311 #1 0x0832451b in RelationClearRelation (relation=3D0x96617200, rebuild=3D<= value optimized out>) at relcache.c:1901 #2 0x08324b9f in RelationFlushRelation () at relcache.c:1991 #3 RelationCacheInvalidateEntry (relationId=3D276951) at relcache.c:2042 #4 0x0831dd89 in LocalExecuteInvalidationMessage (msg=3D0xa21c328) at inva= l.c:510 #5 0x0831d341 in ProcessInvalidationMessages (hdr=3D0xa2075fc, func=3D0x83= 1dc50 <LocalExecuteInvalidationMessage>) at inval.c:397 #6 0x0831d3dc in CommandEndInvalidationMessages () at inval.c:1006 #7 0x080c9035 in AtCommit_LocalCache () at xact.c:1009 #8 CommandCounterIncrement () at xact.c:634 #9 0x0826dcc9 in finish_xact_command () at postgres.c:2363 #10 0x0826ed4d in exec_simple_query ( query_string=3D0xa1e89ec "insert into pch_oid_archive (url, product_nam= e, oid) select product_combined_history_names.url, product_combined_history= _names.product_name, product_info.oid from product_info, product_combined_h= istor"...) at postgres.c:1022 #11 0x0827042c in PostgresMain (argc=3D4, argv=3D0xa17c740, username=3D0xa1= 7c700 "gb") at postgres.c:3614 #12 0x0823a4d3 in BackendRun () at postmaster.c:3449 #13 BackendStartup () at postmaster.c:3063 #14 ServerLoop () at postmaster.c:1387 #15 0x0823b503 in PostmasterMain (argc=3D4, argv=3D0xa179678) at postmaster= .c:1040 #16 0x081dc0a6 in main (argc=3D4, argv=3D0xa179678) at main.c:188 (gdb)=20 Thanks, Rusty - Rusty Conover rconover@infogears.com InfoGears Inc / GearBuyer.com / FootwearBuyer.com http://www.infogears.com http://www.gearbuyer.com http://www.footwearbuyer.com
В списке pgsql-bugs по дате отправления: