From: | John Naylor <jcnaylor(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: docs: outdated reference to recursive expression evaluation |
Date: | 2018-12-10 14:55:11 |
Message-ID: | CAJVSVGVtO=EKCto8g3sktz83BUh278Gd5cXQ3Ly3fgKyiihusQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/8/18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> John Naylor <jcnaylor(at)gmail(dot)com> 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 change in expression evaluation in v10, there's probably a
>> better example of recursive routines, but I'm not sure what that would
>> be.
>
> 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 agree. If you like, here's a patch to leave out the example.
-John Naylor
Attachment | Content-Type | Size |
---|---|---|
remove-reference-to-expr-eval.patch | text/x-patch | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-12-10 15:12:54 | Reorganize collation lookup time and place |
Previous Message | John Naylor | 2018-12-10 14:49:24 | Re: automatically assigning catalog toast oids |