Re: Backend crash in 8.2.3 with plpgsql function - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: Backend crash in 8.2.3 with plpgsql function
Date
Msg-id 20070315144035.GJ5645@alvh.no-ip.org
Whole thread Raw
In response to Backend crash in 8.2.3 with plpgsql function  (SM <sm@resistor.net>)
List pgsql-bugs
SM wrote:

> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /usr/libexec/ld.so...done.
> Reading symbols from /usr/lib/libm.so.1.0...done.
> Reading symbols from /usr/lib/libc.so.29.0...done.
> Reading symbols from /usr/local/pgsql/lib/plpgsql.so...done.
> #0  0x234c2a in hash_search (hashp=0x0, keyPtr=0xcfbfcc50, action=HASH_FIND,
>     foundPtr=0x0) at dynahash.c:782
> 782             return hash_search_with_hash_value(hashp,
> (gdb) bt
> #0  0x234c2a in hash_search (hashp=0x0, keyPtr=0xcfbfcc50, action=HASH_FIND,
>     foundPtr=0x0) at dynahash.c:782
> #1  0x4038ac25 in plpgsql_HashTableLookup (func_key=0xcfbfcc50)
>     at pl_comp.c:2092

Note that "hashp" (which is plpgsql_HashTable) is NULL here ... how can
that be?  The only way I see is that _PG_init was not called.  Maybe
there is a race condition?


--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: johan.walles@gmail.com
Date:
Subject: How to report bugs?
Next
From: Reece Hart
Date:
Subject: Re: Backend crash in 8.2.3 with plpgsql function