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

Re: unexpected and reproducable crash in pl/pgsql function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
Cc: pgsql-hackers-win32(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: unexpected and reproducable crash in pl/pgsql function
Date: 2005-03-03 21:20:00
Message-ID: 13523.1109884800@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> Ok, problem was due to recursive pl/pgsql function and a recursion loop
> in the data.  I traced this problem to the data: somebody disabled the
> recursion check constraint.  
> I've never had this actually happen before.  It totally nuked the
> server.

I thought we'd fixed things so that the stack depth on Windows is
actually greater than max_stack_depth?  None of this weirdness could
happen if the stack depth check were kicking in properly.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Merlin MoncureDate: 2005-03-03 21:28:01
Subject: Re: unexpected and reproducable crash in pl/pgsql function
Previous:From: Tom LaneDate: 2005-03-03 21:17:00
Subject: Re: logging as inserts

pgsql-hackers-win32 by date

Next:From: Merlin MoncureDate: 2005-03-03 21:28:01
Subject: Re: unexpected and reproducable crash in pl/pgsql function
Previous:From: Merlin MoncureDate: 2005-03-03 21:03:11
Subject: Re: unexpected and reproducable crash in pl/pgsql function

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