Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Balamurugan Mahendran <balamurugan(at)adaptavant(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme
Date: 2010-11-27 16:23:46
Message-ID: 9739.1290875026@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-bugs

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Where does your uniqueidentifier.so file come from? It's not a part of
> standard PostgreSQL 9.0, and this is the part that's crashing..

There used to be a project of that name on gborg. I can't find the
source code anymore though.

> Any chance it's a third party module that you didn't recompile for 9.0?

The magic-block mechanism should prevent that. What I'm wondering about
is whether the input function is (a) careless about null input and (b)
not marked STRICT.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Joshua Tolley 2010-11-27 21:11:50 Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme
Previous Message Bruce Momjian 2010-11-27 16:10:27 Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running