From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
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 14:33:49 |
Message-ID: | 24960.1285166029@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
subham(at)cse(dot)iitb(dot)ac(dot)in writes:
> How can I increase the stack depth limit ? Is it only by modifying the
> postgres.conf file, but there I cannot increase the stack depth beyond 4
> MB.
> Actually, my problem is that, when I set the stack base address of the
> child thread using the POSIX library function "pthread_setstackaddr()", I
> am unable to access the memory contents of its parent.
You've got worse problems than the stack depth limit. Creating multiple
threads inside a backend process is entirely unsupported and just about
guaranteed to result in massive breakage. Don't do it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-22 14:45:30 | Re: SQLSTATE of notice PGresult |
Previous Message | Andrew Dunstan | 2010-09-22 14:33:39 | Re: Git cvsserver serious issue |