On Wednesday, October 8, 2003, at 03:54 PM, Tom Lane wrote:

This is probably now solved. Time will tell, since the crashes were
unpredictable to start with.

Bizarrely, it came down to an infinite recursion in a plpgsql function
we were using which exhausted memory and crashed the db server. Is
there any way of limiting stack depth/having some sort of monitor on
these functions to prevent this behaviour in future? Intuitively it
seems to me that dodgy plpgsql functions should not be able to crash
the database server (unlike dodgy C functions, say!).

The offending function was not reported in the logs on Mac OS X for
some reason but only when we compiled a new version on an x86 linux box
(with --enable-debug --enable-cassert, admittedly).

Thanks for listening!
Gareth


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Gareth Boden <gareth.boden (AT) egsgroup (DOT) com> writes:
There's been some talk of this, but the sticking point has been to
figure out a reasonably portable way to measure and enforce stack
usage...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend