Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oWFds-0007Vf-HD for pgsql-committers@arkaria.postgresql.org; Thu, 08 Sep 2022 11:24:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oWFdr-0001I7-9y for pgsql-committers@arkaria.postgresql.org; Thu, 08 Sep 2022 11:24:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oWFdr-0001Hy-29 for pgsql-committers@lists.postgresql.org; Thu, 08 Sep 2022 11:24:19 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oWFdp-0003La-1X for pgsql-committers@lists.postgresql.org; Thu, 08 Sep 2022 11:24:18 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EA2B95C01AB; Thu, 8 Sep 2022 07:24:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 08 Sep 2022 07:24:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1662636255; x=1662722655; bh=F UCKpAhrOgW+SrUgdW/0MCQIxI/50yY9wzLguaVeNSI=; b=XW2WqDeomEtl7yf0T rRKyFEJSfyzkYFoiPKYP3arqXwoVTuI4r7xU3T9YM0aEnitxhCpnEBP3uf+H6aX1 i4FR5raj1oN0+Ccf7coamnEsq3C6NQ6PMy/SQg2Ae2gWyUtzfMAnU3Vc5xVd/y1f 7pKJI0cm30bPpOaHCSWq7z8KyAx7Ps+GDOL8okrqIYc6s3IhCFXGhTmQpF2pcp2i gh6JfVh9e2rDzuGdgJU3DHN4eljIQ06O+nEFgYTclyVPGZtp1ceOB6gbQfh+VG6c pH7O+i9/B6ptRADffLJFM95xAsDinFAbcOtOayTMbbfTPRAqQ0J/pXjvA8oPlRDK CGm+Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfedtvddggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepfeejgeehteeuhfevvedu leeufedtjeetiefftedvudfhtdeifefgueettdevgefgnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhht segvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 8 Sep 2022 07:24:15 -0400 (EDT) Message-ID: Date: Thu, 8 Sep 2022 13:24:14 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: pgsql: doc: clarify recursion internal behavior Content-Language: en-US To: Bruce Momjian , pgsql-committers@lists.postgresql.org References: From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 03.09.22 03:58, Bruce Momjian wrote: > doc: clarify recursion internal behavior - Strictly speaking, this process is iteration not recursion, but - RECURSIVE is the terminology chosen by the SQL standards - committee. + While RECURSIVE allows queries to be specified + recursively, internally all queries are evaluated iteratively. Is that true? Surely there is some recursive behavior in the executor.