| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Alexander Wöhrer <woehrer(at)par(dot)univie(dot)ac(dot)at> |
| Cc: | pljava-dev(at)pgfoundry(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [Pljava-dev] stack depth limit exceeded - patch possible? |
| Date: | 2008-04-13 14:25:54 |
| Message-ID: | Pine.BSO.4.64.0804131023000.9928@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pljava-dev |
On Sat, 12 Apr 2008, Alexander Whrer wrote:
> I'm working on Windows XP SP2 (stack limit 3500 kb) and deployed
> successfully my application (doing some external Web service calling)
> inside PostGre 8.3.0.
>
> Unfortunatelly, the application needs at least 3 Threads and will run
> for quite some time.
>
> I found this comment
>
> http://pgfoundry.org/pipermail/pljava-dev/2005/000491.html
>
> by Thomas Hallgren where he mentioned that PostGre only defines
> one stack and therefor pl/java has no way of telling PostGre
> about multiple thread stack pointers.
>
> My question is now if there is a patched version available of PostGre
> 8.3.0 having this stack_depth check disabled?
This was fixed in postgresql/pljava shortly after the referenced
discussion. As requested, postgresql 8.1+ allows modification of
stack_base_ptr so pljava can set it as desired.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2008-04-13 15:09:07 | Re: Cached Query Plans (was: global prepared statements) |
| Previous Message | PFC | 2008-04-13 12:26:04 | Re: Cached Query Plans (was: global prepared statements) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Wöhrer | 2008-04-14 12:56:51 | Re: [Pljava-dev] stack depth limit exceeded - patch possible? |
| Previous Message | Alexander Wöhrer | 2008-04-12 18:51:05 | [Pljava-dev] stack depth limit exceeded - patch possible? |