Re: Needs Suggestion

From: subham(at)cse(dot)iitb(dot)ac(dot)in
To: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: subham(at)cse(dot)iitb(dot)ac(dot)in, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Needs Suggestion
Date: 2010-09-22 09:30:01
Message-ID: 5bd97b9da99ae65a7607d116494c70f6.squirrel@www.cse.iitb.ac.in
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


So, Can I increase the stack depth limit to a large value ?

> On 22/09/10 12:03, subham(at)cse(dot)iitb(dot)ac(dot)in wrote:
>> Actually, I used palloc() to set the stack base address.
>> And I am trying to create only a single thread, then also it is causing
>> problem.
>> Actually, I created all the data-structures using palloc(), then I am
>> passing these to the child thread. Even if I make these variables global
>> then also it is not working.
>> But if I don't set its stack address then it is working. But I need to
>> do
>> that because when my thread body is big then it is causing stack fault.
>> So if I cannot set its stack address then Can I increase the stack depth
>> limit to a large value ?
>
> It's not clear what you're trying to do, but it's just not going to
> work. The backend code is not thread-safe, so you can't safely create
> any threads in server code. Not even a single one. And even if you
> could, you should not mess with stack base addresses.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>

--

Thank You,
Subham Roy.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-09-22 09:45:22 Re: BUG #5661: The character encoding in logfile is confusing.
Previous Message Peter Eisentraut 2010-09-22 09:29:05 Re: snapshot generation broken