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 1ufPOo-006sYy-Qz for pgsql-general@arkaria.postgresql.org; Fri, 25 Jul 2025 20:52:15 +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 1ufPOn-004lqG-VI for pgsql-general@arkaria.postgresql.org; Fri, 25 Jul 2025 20:52:14 +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 1ufPOn-004lq8-L3 for pgsql-general@lists.postgresql.org; Fri, 25 Jul 2025 20:52:13 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ufPOm-000mDw-0Q for pgsql-general@lists.postgresql.org; Fri, 25 Jul 2025 20:52:12 +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 56PKq9Fi2223786; Fri, 25 Jul 2025 16:52:09 -0400 From: Tom Lane To: Laurenz Albe cc: Rumpi Gravenstein , PostgreSQL Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array In-reply-to: References: <1934172.1753462470@sss.pgh.pa.us> <1936547.1753463422@sss.pgh.pa.us> <1940680.1753465819@sss.pgh.pa.us> <1943137.1753467040@sss.pgh.pa.us> Comments: In-reply-to Laurenz Albe message dated "Fri, 25 Jul 2025 22:44:35 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2223784.1753476729.1@sss.pgh.pa.us> Date: Fri, 25 Jul 2025 16:52:09 -0400 Message-ID: <2223785.1753476729@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Laurenz Albe writes: > On Fri, 2025-07-25 at 14:10 -0400, Tom Lane wrote: >> So ... any chance you have a data type named _sa_setup_role? > ... it could also be a type "sa_setup_role", and "_sa_setup_role" > is interpreted as the corresponding array type: Oh, of course --- that's a good deal more likely than my version. regards, tom lane