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 1ufLwA-00661G-66 for pgsql-general@arkaria.postgresql.org; Fri, 25 Jul 2025 17:10:26 +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 1ufLw9-0038P3-9i for pgsql-general@arkaria.postgresql.org; Fri, 25 Jul 2025 17:10:25 +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 1ufLw8-0038Ov-WB for pgsql-general@lists.postgresql.org; Fri, 25 Jul 2025 17:10:25 +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 1ufLw7-000khG-28 for pgsql-general@lists.postgresql.org; Fri, 25 Jul 2025 17:10:24 +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 56PHAMDP1936548; Fri, 25 Jul 2025 13:10:22 -0400 From: Tom Lane To: Rumpi Gravenstein cc: 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> Comments: In-reply-to Rumpi Gravenstein message dated "Fri, 25 Jul 2025 12:59:59 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1936546.1753463422.1@sss.pgh.pa.us> Date: Fri, 25 Jul 2025 13:10:22 -0400 Message-ID: <1936547.1753463422@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Rumpi Gravenstein writes: > No ... just one version: D'oh, actually this would have complained if there was more than one match, so that theory is wrong: > xxxx_pub_dev_2_db=# DROP FUNCTION if exists _sa_setup_role; > DROP FUNCTION Now I'm wondering about stray entries in pg_cast. Also, do you have any extensions loaded in that DB that aren't in your other ones? regards, tom lane