Skip site navigation (1) Skip section navigation (2)

BUG #5412: Crash in production SIGSEGV, equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x966508c4) at tupdesc.c

From: "Rusty Conover" <rconover(at)infogears(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5412: Crash in production SIGSEGV, equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x966508c4) at tupdesc.c
Date: 2010-04-09 13:13:38
Message-ID: 201004091313.o39DDc21082019@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
The following bug has been logged online:

Bug reference:      5412
Logged by:          Rusty Conover
Email address:      rconover(at)infogears(dot)com
PostgreSQL version: 8.4.3
Operating system:   Fedora Core 10, 2.6.27.30-170.2.82.fc10.i686.PAE
Description:        Crash in production SIGSEGV, equalTupleDescs
(tupdesc1=0x7f7f7f7f, tupdesc2=0x966508c4) at tupdesc.c
Details: 

Hi,

8.4.3 is crashing for me under load, below is the stack trace:

#0  equalTupleDescs (tupdesc1=0x7f7f7f7f, tupdesc2=0x966508c4) at
tupdesc.c:311
#1  0x0832451b in RelationClearRelation (relation=0x96654178, rebuild=<value
optimized out>) at relcache.c:1901
#2  0x08324b9f in RelationFlushRelation () at relcache.c:1991
#3  RelationCacheInvalidateEntry (relationId=322615) at relcache.c:2042
#4  0x0831dd89 in LocalExecuteInvalidationMessage (msg=0xa218b54) at
inval.c:510
#5  0x0831d341 in ProcessInvalidationMessages (hdr=0xa2010c4, 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=0xa1e88d4 "insert into product_refer_urls (item_id,
destination_url) select product_info.oid,  product_info_static.affiliate_url
from real_products, product_parts, product_info left join
product_info_static on ("...) at postgres.c:1022
#11 0x0827042c in PostgresMain (argc=4, argv=0xa17c5d0, username=0xa17c590
"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

The bug is reproducible, I'm not sure how to proceed.  Here is the output
from the log:

LOG:  server process (PID 8886) was terminated by signal 11: Segmentation
fault
LOG:  terminating any other active server processes
WARNING:  terminating connection because of crash of another server process

I have been seeing these messages:

LOG:  autovacuum: found orphan temp table "pg_temp_7"."found_sizes" in
database "gb_render_footwear_db"
LOG:  autovacuum: found orphan temp table "pg_temp_7"."classification_tree"
in database "gb_render_footwear_db"

Could they be the result of previous crashes?  Any help is greatly
appreciated.

All of this code ran perfectly under 8.3.

Thanks,

Rusty

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2010-04-09 13:16:58
Subject: is_absolute_path incorrect on Windows
Previous:From: Necati BaturDate: 2010-04-09 13:10:17
Subject: Re: GSOC PostgreSQL partitioning issue

pgsql-bugs by date

Next:From: Andy BalholmDate: 2010-04-09 14:33:14
Subject: Re: bugs that have not been replied-to on list
Previous:From: Robert HaasDate: 2010-04-09 12:08:03
Subject: Re: bugs that have not been replied-to on list

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group