| From: | Oleg Jurtšenko <oleg(dot)jurtsenko(at)fts(dot)ee> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5235: Segmentation fault under high load through JDBC |
| Date: | 2009-12-08 20:08:10 |
| Message-ID: | 4B1EB22A.7020403@fts.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
You are right, it crushes on following statement: "select
instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual;"
max_stack_depth is commented out, I think it has the default value: #max_stack_depth = 2MB
I'm attaching related functions.
Oleg
Robert Haas wrote:
> 2009/12/8 Oleg Jurtšenko <oleg(dot)jurtsenko(at)fts(dot)ee>:
>
>> Once more:
>>
>> http://www.fts.ee/pgsqldebug.tgz - with loging enabled
>> http://www.ftse.ee/pg_core.tar.bzip2 - full core dump
>>
>
> It looks like you've got a pl/pgsql function that called itself
> recursively 1417 times before running out of stack space. What do you
> have max_stack_depth set to?
>
> ...Robert
>
| Attachment | Content-Type | Size |
|---|---|---|
| OB2.50MP9_functions.txt | text/plain | 5.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcelo Mas | 2009-12-08 21:21:58 | BUG #5236: Aparent bug in ecpg |
| Previous Message | Robert Haas | 2009-12-08 19:42:05 | Re: BUG #5235: Segmentation fault under high load through JDBC |