Re: BUG #1473: Backend bus error, possibly due to ANALYZE - Mailing list pgsql-bugs

From Brian B.
Subject Re: BUG #1473: Backend bus error, possibly due to ANALYZE
Date
Msg-id 20050212041337.GA43654@bbdab.org
Whole thread Raw
In response to Re: BUG #1473: Backend bus error, possibly due to ANALYZE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #1473: Backend bus error, possibly due to ANALYZE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Feb 11, 2005 at 10:33:00PM -0500, Tom Lane wrote:
> BTW, something that would be interesting is to figure out what the
> thread stack size actually is (I assume this is available in the FreeBSD
> docs) and experiment to find what is the maximum value max_stack_depth
> can be set to without letting infinite_recurse() dump core.

You may be onto something, there. After doing some searching, I have
found the FreeBSD thread stack size as a default of 64KB! After Googling
for things like "freebsd thread stack size set", it seems other projects are
running into this situation with FreeBSD, as well as FreeBSD mailinglist
chatter about the philosophy behind proper stack usage and whether to just
match Linux's settings for this.

Some notable topics on the matter, being:

(Question about our default pthread stack size)
http://lists.freebsd.org/pipermail/freebsd-threads/2004-November/002699.html

([PATCH] Dynamic thread stack size)
http://lists.freebsd.org/pipermail/freebsd-threads/2005-January/002793.html

Search results showed several other projects having this issue. Some
try to workaround the problem by calling pthread_attr_setstacksize and using
a value anywhere from a default doubling (of 128KB) up to around 1MB.


Thanks,

Brian B.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #1473: Backend bus error, possibly due to ANALYZE
Next
From: Tom Lane
Date:
Subject: Re: BUG #1473: Backend bus error, possibly due to ANALYZE