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 <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1ufLk5-006394-Ej
	for pgsql-general@arkaria.postgresql.org; Fri, 25 Jul 2025 16:57:58 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1ufLk4-002u76-Hk
	for pgsql-general@arkaria.postgresql.org; Fri, 25 Jul 2025 16:57:56 +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 <tgl@sss.pgh.pa.us>)
	id 1ufLgq-002oQH-48
	for pgsql-general@lists.postgresql.org; Fri, 25 Jul 2025 16:54:36 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1ufLgl-000oA9-1z
	for pgsql-general@lists.postgresql.org;
	Fri, 25 Jul 2025 16:54:35 +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 56PGsUPS1934173;
	Fri, 25 Jul 2025 12:54:30 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rumpi Gravenstein <rgravens@gmail.com>
cc: PostgreSQL <pgsql-general@lists.postgresql.org>
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
In-reply-to: <CAEpg1wBxp=25isxj6yt2cf97KtvbwxvJfrJ9qYF8UQxGSBJ93Q@mail.gmail.com>
References: <CAEpg1wBxp=25isxj6yt2cf97KtvbwxvJfrJ9qYF8UQxGSBJ93Q@mail.gmail.com>
Comments: In-reply-to Rumpi Gravenstein <rgravens@gmail.com>
	message dated "Fri, 25 Jul 2025 12:36:23 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1934171.1753462470.1@sss.pgh.pa.us>
Date: Fri, 25 Jul 2025 12:54:30 -0400
Message-ID: <1934172.1753462470@sss.pgh.pa.us>
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/1934172.1753462470%40sss.pgh.pa.us>
Precedence: bulk

Rumpi Gravenstein <rgravens@gmail.com> writes:
> I've been confound by the following behavior that I see in one of our
> PostgreSQL 16 instances.  In this case I am running this script from psql.

I'd bet there is another function named _sa_setup_role() that takes
some kind of array, and the parser is resolving the ambiguity by
choosing that one.

"\df _sa_setup_role" would be illuminating.

			regards, tom lane