| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | 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-08-24 17:58:04 |
| Message-ID: | ee0a326f-d358-16f2-8dbb-a5172f982142@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2022-08-26 09:05:14 | No backup history file found |
| Previous Message | PG Doc comments form | 2022-08-23 14:38:13 | Typo in docs for "recovery_init_sync_method" parameter. |