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 1lrT1r-0005AC-Hu for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Jun 2021 22:19:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lrT1o-0007xN-Qd for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Jun 2021 22:19:56 +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 1lrT1o-0007xE-K0 for pgsql-bugs@lists.postgresql.org; Thu, 10 Jun 2021 22:19:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lrT1m-0007FZ-7Y for pgsql-bugs@lists.postgresql.org; Thu, 10 Jun 2021 22:19:56 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 15AMJpej1806870; Thu, 10 Jun 2021 18:19:51 -0400 From: Tom Lane To: zpetukhov@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17057: Unexpected error: ERROR: unsupported target type: 0 In-reply-to: <17057-5ddf70c25e23468f@postgresql.org> References: <17057-5ddf70c25e23468f@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 10 Jun 2021 21:46:10 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1806868.1623363591.1@sss.pgh.pa.us> Date: Thu, 10 Jun 2021 18:19:51 -0400 Message-ID: <1806869.1623363591@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > I faced with an odd error while developing a stored procedure with > transaction control inside. Hi, this works fine for me on all branches back to v11. I get NOTICE: ! 7 NOTICE: ! 7 NOTICE: ! 77 which looks like the correct behavior. I suspect you're hitting the bug fixed in commit 0ea25ed10, so you need to update to 13.2 or later. regards, tom lane