Re: server process segfaulting

From: James Gregory <james(at)anchor(dot)net(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: server process segfaulting
Date: 2003-05-15 02:18:54
Message-ID: 1052965133.6435.57.camel@pirate.bridge.anchor.net.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 2003-05-15 at 01:53, Tom Lane wrote:
> James Gregory <james(at)anchor(dot)net(dot)au> writes:
> > The logs from the point where it is dying are below. The last queries
> > before the segfault are coming from a trigger I wrote in plpython to do
> > referential integrity checking for inherited tables (I posted about it
> > before writing said code).
>
> Um. There was a report that plpython triggers get confused if you try
> to apply the same trigger procedure to multiple tables (it tries to use
> the first table's row descriptor with all the other tables, and yes that
> can lead to a segfault).

Is it only plpython that has the problem? If I wanted to fix this where
would I start looking? presumably pgsql/src/plpython/plpython.c. Do you
have a link with more info about the bug by any chance?

Many thanks for your help. My code is exhibiting exactly that behaviour,
so it sounds like that's what the problem is.

James.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-05-15 02:39:07 Re: server process segfaulting
Previous Message Alvaro Herrera 2003-05-15 02:02:57 Re: fomatting an interval (resend)