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 1r3AcM-002TCm-Ba for pgsql-bugs@arkaria.postgresql.org; Wed, 15 Nov 2023 07:47:22 +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 1r3AcK-00EanH-54 for pgsql-bugs@arkaria.postgresql.org; Wed, 15 Nov 2023 07:47:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r3AcJ-00Ean9-S5 for pgsql-bugs@lists.postgresql.org; Wed, 15 Nov 2023 07:47:19 +0000 Received: from h55.sserv.ru ([95.215.177.133]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r3AcD-005f9F-7i for pgsql-bugs@lists.postgresql.org; Wed, 15 Nov 2023 07:47:18 +0000 Received: from [194.190.106.52] (helo=kulakov) by h55.sserv.ru with esmtpa (Exim 4.92.3) (envelope-from ) id 1r3AcA-0007nd-OJ for pgsql-bugs@lists.postgresql.org; Wed, 15 Nov 2023 10:47:10 +0300 From: "Pavel Kulakov" To: References: <18195-95ee8b48a9d7cd93@postgresql.org> <2486681.1699975861@sss.pgh.pa.us> In-Reply-To: Subject: RE: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement Date: Wed, 15 Nov 2023 10:47:10 +0300 Message-ID: <001901da1797$f0bd4f90$d237eeb0$@systematica.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: ru Thread-Index: AQHU2ZXcvcQNKHg1XihmYBUfGbDXmQI/xV33sHN1/MCAAAOScIAAA9cQ List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This also permits the following syntax in PL/pgSQL: do $sql$ declare _s text; begin _s = '1' somegarbage; end; $sql$; I understand why it works. But it looks really strange.