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

Re: Trigger causes the server to crash with SEGV

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: vlad(at)crystalballinc(dot)com
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: Trigger causes the server to crash with SEGV
Date: 2001-06-01 19:17:05
Message-ID: 6515.991423025@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
I tried it here.  I don't get a crash; I get a rather long delay and
then

psql:vlad.sql:61: NOTICE:  Error occurred while executing PL/pgSQL function sp_loc_parent_check
psql:vlad.sql:61: NOTICE:  line 12 at return
psql:vlad.sql:61: ERROR:  Memory exhausted in AllocSetContextCreate(8192)

which is not too surprising seeing that your function is in an infinite
recursion (chasing the loop 96 -> 15 -> 3 -> 96 that your insert has
created).

It would be interesting to know why your copy SEGV's rather than
recovering gracefully.  Can you provide a debugger backtrace from the
coredump?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2001-06-01 20:56:20
Subject: Re: Trigger causes the server to crash with SEGV
Previous:From: Tom LaneDate: 2001-06-01 17:09:43
Subject: Re: Trigger causes the server to crash with SEGV

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