| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> | 
|---|---|
| To: | subham(at)cse(dot)iitb(dot)ac(dot)in | 
| Cc: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: Needs Suggestion | 
| Date: | 2010-09-22 09:10:34 | 
| Message-ID: | 4C99C80A.9010002@enterprisedb.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-09-22 09:29:05 | Re: snapshot generation broken | 
| Previous Message | subham | 2010-09-22 09:03:51 | Re: Needs Suggestion |