From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Drew DeVault <sir(at)cmpwn(dot)com>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] doc/queries.sgml: add missing comma |
Date: | 2022-09-03 01:58:16 |
Message-ID: | YxK0uKKpsCex/IsO@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Aug 30, 2022 at 02:18:42PM -0400, Bruce Momjian wrote:
> On Wed, Aug 24, 2022 at 07:58:04PM +0200, Peter Eisentraut wrote:
> > On 18.08.22 20:10, Bruce Momjian wrote:
> > > > Thus:
> > > > Strictly speaking, this process is iteration, but <literal>RECURSIVE</literal>
> > > > is the terminology chosen by the SQL standards committee."
> > > >
> > > > Because the above sounds just fine, I'd argue that if one does leave "not
> > > > recursion" it should be set off by a comma.
> > > I went with new wording, which should make this even clearer; patch
> > > attached.
> >
> > I think this whole note is a bit misleading, like the SQL people don't know
> > what recursion is. The point is that the query is defined recursively. The
> > evaluation process is iterative. Those two are not contradictions.
>
> Okay, makes sense. Here is an updated patch.
Patch applied back to PG 10.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2022-09-03 03:32:32 | Re: Duplicate text in ANALYZE related to inheritance/parents |
Previous Message | guyren@relevantlogic.com | 2022-09-02 22:28:19 | Re: No discussion of custom variables; no "See also" for set_config, current_setting, pg_settings |