"Merlin Moncure" <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org