Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1saR0r-008m1n-9l for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Aug 2024 02:30:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1saR0p-007oEh-Ew for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Aug 2024 02:30:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1saR0p-007oEK-3L for pgsql-hackers@lists.postgresql.org; Sun, 04 Aug 2024 02:30:23 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1saR0m-0031Hs-Fn for pgsql-hackers@lists.postgresql.org; Sun, 04 Aug 2024 02:30:22 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=pBUnxbLllBL83azFgi+RoE/Uoudq7WvjAJhfZfBL1Eo=; b=qOpnOhTHqNxhwqnnD3Y7oRPk2Q 0xfQc25/UHiK9BW8pbM2Erb3E+RJt6QWK0NTe3/pacV3i7XQHa8kLtVnfgOjmM3849wQVyzrm1zOf ZfWs6bpbywejKtpux4BAPEGW1EOydOELPCrbb5fhjIAJ/sPjd5QPh57w+omFK4ZqGfXYAFsL21+Va m/yNLCQ4eoWxqlaMUUGXi7jR1n0FA2ozT1kDoCurvpKuGx/eAluRg0CDXW+T41HLo6geM0wQeW/fg EpDRBCOOHdG1hmbcK9riVQOCNJIGHavEapL3ksr8Vn3OvczFHRwEIY15WLCs8gUAMqsJ7HGjY+Chu sg0bGzvA==; Received: from [2409:11:4120:300:ed81:a0e8:a3a2:1055] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (Exim 4.94.2) (envelope-from ) id 1saR0j-007iAS-LC; Sun, 04 Aug 2024 02:30:20 +0000 Date: Sun, 04 Aug 2024 11:30:09 +0900 (JST) Message-Id: <20240804.113009.130888580400999969.ishii@postgresql.org> To: tgl@sss.pgh.pa.us Cc: pgsql-hackers@lists.postgresql.org Subject: Re: subquery and sub-SELECT From: Tatsuo Ishii In-Reply-To: <292155.1722738132@sss.pgh.pa.us> References: <20240804.104807.1230474056016095674.ishii@postgresql.org> <292155.1722738132@sss.pgh.pa.us> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:ed81:a0e8:a3a2:1055 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Tatsuo Ishii writes: >> In our documentations, "subquery", "sub-query", "sub-select" and >> "sub-SELECT" are used. In English, are they interchangeable? > > Pretty nearly. I think "sub-query" can include DML such as > INSERT RETURNING, whereas "sub-select" should only be a SELECT. > (I'm not claiming that we've been perfectly accurate about > that distinction.) The dashes definitely don't matter. That makes sense. Thanks for the explanation! -- Tatsuo Ishii SRA OSS LLC English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp