Re: Checking max_stack_depth automatically - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Checking max_stack_depth automatically
Date
Msg-id 24448.1160326459@sss.pgh.pa.us
Whole thread Raw
In response to Re: Checking max_stack_depth automatically  ("Magnus Hagander" <mha@sollentuna.net>)
List pgsql-hackers
"Magnus Hagander" <mha@sollentuna.net> writes:
>> 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?

I think we'd have to put the define in Makefile.global, which seems like
overkill ... but OTOH, seeing that it's textually in two places in
backend/Makefile already, maybe that's the best way.  The alternative is
to stick a comment in each place referencing the other(s) ...

>> 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..)

I agree, that's right out.  Hardwired it shall be.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: Checking max_stack_depth automatically
Next
From: "Jim C. Nasby"
Date:
Subject: Re: timestamptz alias