Re: docs: outdated reference to recursive expression evaluation

2018-12-10 Thread Tom Lane
John Naylor writes: > On 12/8/18, Tom Lane wrote: >> We could say "expression compilation" and it'd still be valid. Or just >> drop the last four words altogether. I don't think we want to expend the >> verbiage to be more precise here, since it's only a tangential point. > I'm inclined to

Re: docs: outdated reference to recursive expression evaluation

2018-12-10 Thread John Naylor
On 12/8/18, Tom Lane wrote: > John Naylor writes: >> In confg.sgml, in the section about max_stack_depth, there's this >> sentence: >> "The safety margin is needed because the stack depth is not checked in >> every routine in the server, but only in key potentially-recursive >> routines such as

Re: docs: outdated reference to recursive expression evaluation

2018-12-08 Thread Tom Lane
John Naylor writes: > In confg.sgml, in the section about max_stack_depth, there's this sentence: > "The safety margin is needed because the stack depth is not checked in > every routine in the server, but only in key potentially-recursive > routines such as expression evaluation." > Since the

docs: outdated reference to recursive expression evaluation

2018-12-08 Thread John Naylor
In confg.sgml, in the section about max_stack_depth, there's this sentence: "The safety margin is needed because the stack depth is not checked in every routine in the server, but only in key potentially-recursive routines such as expression evaluation." Since the change in expression evaluation