Re: BUG #5235: Segmentation fault under high load through JDBC - Mailing list pgsql-bugs

From Andrew Gierth
Subject Re: BUG #5235: Segmentation fault under high load through JDBC
Date
Msg-id 87vdgg9uad.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: BUG #5235: Segmentation fault under high load through JDBC  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: BUG #5235: Segmentation fault under high load through JDBC  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-bugs
>>>>> "Robert" == Robert Haas <robertmhaas@gmail.com> writes:

 Robert> How about (3) getrlimit(RLIMIT_STACK) lies through its teeth,
 Robert> by ignoring the existence of another and lower limit imposed
 Robert> elsewhere?

 Robert> A little Googling seems to reveal that FreeBSD has a
 Robert> parameter called MAXSSIZ (and possibly a variant for 64-bit
 Robert> builds).  I kind find a lot of people talking about needing
 Robert> to raise it (for MySQL, among other things), but I haven't
 Robert> been able to determine for certain what the default is.
 Robert> Perhaps it is set to a really low value on the OP's system?

The default is 64MB on i386, 512MB on amd64; that's where the
getrlimit value comes from unless it's been explicitly reduced
somewhere. The kernel MAXSSIZ sets the value of the hard limit for
RLIMIT_STACK for proc0, and everything else inherits that. All
setrlimit calls for RLIMIT_STACK are explicitly clamped to MAXSSIZ, so
there's no way to set that value higher than the kernel limit, and no
way for getrlimit to report a value higher than the real limit.

--
Andrew (irc:RhodiumToad)

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #5235: Segmentation fault under high load through JDBC
Next
From: Andrew Gierth
Date:
Subject: Re: BUG #5235: Segmentation fault under high load through JDBC