| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Robert Haas <robertmhaas(at)gmail(dot)com>, Oleg Jurtšenko <oleg(dot)jurtsenko(at)fts(dot)ee>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5235: Segmentation fault under high load through JDBC |
| Date: | 2009-12-09 14:43:09 |
| Message-ID: | 1588.1260369789@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> I vaguely recall issues in the past with linking of postgresql (or PLs
> that require it) against libc_r causing some rather small stack limits
> being imposed under some circumstances but I don't recall the details
> any more...
Yeah, we've seen cases where libc suddenly decided to impose a "per
thread" stacksize limit on the process's main (only) stack. I don't
recall what the triggering conditions were.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2009-12-09 15:56:23 | Re: BUG #5235: Segmentation fault under high load through JDBC |
| Previous Message | Stefan Kaltenbrunner | 2009-12-09 14:11:13 | Re: BUG #5235: Segmentation fault under high load through JDBC |