Re: Backend crash in 8.2.3 with plpgsql function

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: SM <sm(at)resistor(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Backend crash in 8.2.3 with plpgsql function
Date: 2007-03-15 14:40:35
Message-ID: 20070315144035.GJ5645@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Gaetano Mendola 2007-03-15 14:52:47 Re: Backend crash in 8.2.3 with plpgsql function
Previous Message Tom Lane 2007-03-15 05:40:54 Re: Backend crash in 8.2.3 with plpgsql function

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-03-15 14:45:43 Re: Additional global stats for pg_database?
Previous Message Alvaro Herrera 2007-03-15 14:25:57 Re: Additional global stats for pg_database?