Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iX9TB-0007JI-Or for pgsql-docs@arkaria.postgresql.org; Tue, 19 Nov 2019 19:47:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iX9TA-0001BI-KT for pgsql-docs@arkaria.postgresql.org; Tue, 19 Nov 2019 19:47:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iX9TA-0001BB-9D for pgsql-docs@lists.postgresql.org; Tue, 19 Nov 2019 19:47:24 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iX9T7-0008NV-42 for pgsql-docs@lists.postgresql.org; Tue, 19 Nov 2019 19:47:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xAJJlGot026944; Tue, 19 Nov 2019 14:47:16 -0500 From: Tom Lane To: Andreas Kretschmer cc: pgsql-docs@lists.postgresql.org Subject: Re: documentation for WITH RECURSIVE In-reply-to: References: <20712.1574098328@sss.pgh.pa.us> <94685a79-0b75-34ad-16bb-e1f23eb28c24@a-kretschmer.de> Comments: In-reply-to Andreas Kretschmer message dated "Tue, 19 Nov 2019 13:29:39 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <26942.1574192836.1@sss.pgh.pa.us> Date: Tue, 19 Nov 2019 14:47:16 -0500 Message-ID: <26943.1574192836@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andreas Kretschmer writes: > it would be good if we can also add this to chapter 7.8, wouldn't it? I don't feel a need to. 7.8 isn't attempting to define the syntax precisely. Moreover, we've had this feature since 8.4, and this is the first I've heard of somebody misinterpreting the syntax; so it doesn't seem like it's a huge problem that requires multiple explanations. I've pushed a patch for the SELECT reference page. regards, tom lane