From: | Rusty Conover <rconover(at)infogears(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5412: Crash in production SIGSEGV, equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x966508c4) at tupdesc.c |
Date: | 2010-04-13 20:38:39 |
Message-ID: | 4B37EAC6-3455-4ADE-99A4-46A37CD1A866@infogears.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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.
>
> How do you reproduce it? Can you make a self-contained test case?
>
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 processes.
I have about 12 different db sessions creating temporary tables with the same 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 temporary tables, its completely separate in a different database.
Here a new crash from today with the same trace:
#0 equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x9661e430) at tupdesc.c:311
311 if (tupdesc1->natts != tupdesc2->natts)
(gdb) bt
#0 equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x9661e430) at tupdesc.c:311
#1 0x0832451b in RelationClearRelation (relation=0x96617200, rebuild=<value optimized out>) at relcache.c:1901
#2 0x08324b9f in RelationFlushRelation () at relcache.c:1991
#3 RelationCacheInvalidateEntry (relationId=276951) at relcache.c:2042
#4 0x0831dd89 in LocalExecuteInvalidationMessage (msg=0xa21c328) at inval.c:510
#5 0x0831d341 in ProcessInvalidationMessages (hdr=0xa2075fc, func=0x831dc50 <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=0xa1e89ec "insert into pch_oid_archive (url, product_name, oid) select product_combined_history_names.url, product_combined_history_names.product_name, product_info.oid from product_info, product_combined_histor"...)
at postgres.c:1022
#11 0x0827042c in PostgresMain (argc=4, argv=0xa17c740, username=0xa17c700 "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=4, argv=0xa179678) at postmaster.c:1040
#16 0x081dc0a6 in main (argc=4, argv=0xa179678) at main.c:188
(gdb)
Thanks,
Rusty
-
Rusty Conover
rconover(at)infogears(dot)com
InfoGears Inc / GearBuyer.com / FootwearBuyer.com
http://www.infogears.com
http://www.gearbuyer.com
http://www.footwearbuyer.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-04-13 21:02:54 | Re: BUG #5418: psql exits after using tab-completion with error message |
Previous Message | Alvaro Herrera | 2010-04-13 19:28:33 | Re: BUG #5418: psql exits after using tab-completion with error message |
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-04-13 20:53:03 | Re: psql's \d display of unique index vs. constraint |
Previous Message | Tom Lane | 2010-04-13 20:00:57 | Re: GSoC - proposal - Materialized Views in PostgreSQL |