From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Checking max_stack_depth automatically |
Date: | 2006-10-08 16:47:30 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA0FC2D@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > For win32, we set the stacksize in src/backend/Makefile with
> > "-Wl,--stack=4194304". So we know at build time what it is, if that
> > helps you...
>
> Well, I can just wire that value into get_stack_depth_rlimit,
> I suppose, but it sounds crocky.
If we do, we probably move it to a define (which could just be in the
Makefile) so we don't accidenally change one without the other, no?
> There's no way to tell at runtime what value was set?
None that I know of, and none that I can find in a quick search of the
API docs. A google shows up a couple of references to other people
saying it can't be done. (Other than opening your own EXE file and
manually parsing the PE header, but that seems at least as bad..) For
example, see the discussion aobut stack attributes at
http://www.roguewave.com/support/docs/hppdocs///thr200pl/8-2.html.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-08 16:54:19 | Re: Checking max_stack_depth automatically |
Previous Message | Tom Lane | 2006-10-08 16:41:04 | Re: Checking max_stack_depth automatically |