=?ISO-8859-1?Q?Alexander_W=F6hrer?= <[EMAIL PROTECTED]> writes:
> I will try my luck anyway and try to built PostGre 8.3 without
> check_stack_depth doing anything - will let you know what happens for my
> application.
It will crash ... but perhaps not until after it's hopelessly corrupted
your
Alexander Wöhrer <[EMAIL PROTECTED]> writes:
> Dear Gregory,
>
> Thank you very much for you fast answer and your tips.
> What is meant by IIUC?
"if I understand correctly"
> Actually just one thread is accessing the database - the two others do
> send/recieve data.
Then in theory it should wor
Dear Gregory,
Thank you very much for you fast answer and your tips.
What is meant by IIUC?
Actually just one thread is accessing the database - the two others do
send/recieve data.
I will try my luck anyway and try to built PostGre 8.3 without
check_stack_depth doing anything - will let you
Alexander Wöhrer <[EMAIL PROTECTED]> writes:
> 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.
>
> As far as I understand the situation, the check_stack_depth()
> is used "just"
Dear PostGre developers,
I'm working on Windows XP SP2 (stack limit set to 3500 kb) and deployed
successfully my Java 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 fou
