From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Checking max_stack_depth automatically |
Date: | 2006-10-08 16:54:19 |
Message-ID: | 24448.1160326459@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Magnus Hagander" <mha(at)sollentuna(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-10-08 17:03:26 | Re: timestamptz alias |
Previous Message | Magnus Hagander | 2006-10-08 16:47:30 | Re: Checking max_stack_depth automatically |