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: <1940680.1753465819@sss.pgh.pa.us>
References: <CAEpg1wBxp=25isxj6yt2cf97KtvbwxvJfrJ9qYF8UQxGSBJ93Q@mail.gmail.com> <1934172.1753462470@sss.pgh.pa.us> <CAEpg1wCDL+iYbG7ByjHcgfvJy7m3m-rDp-xKiYovvxeKTbG7iQ@mail.gmail.com> <1936547.1753463422@sss.pgh.pa.us> <CAEpg1wALRocK=uDSNyJqdc=vhNGjYFmT3H_TNzihSOMS88WHfg@mail.gmail.com> <1940680.1753465819@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Fri, 25 Jul 2025 13:50:19 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1943136.1753467040.1@sss.pgh.pa.us>
Date: Fri, 25 Jul 2025 14:10:40 -0400
Message-ID: <1943137.1753467040@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1943137.1753467040%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Well, there's got to be *something* different about that database.

After looking at the code I remembered that the parser might be taking
this as a type coercion request.  With that idea, I can duplicate the
observed behavior like so:

regression=# select _sa_setup_role('af_repo_app');
INFO:  af_repo_app
 _sa_setup_role 
----------------
 Done
(1 row)

regression=# create domain _sa_setup_role as varchar[];
CREATE DOMAIN
regression=# select _sa_setup_role('af_repo_app');
ERROR:  malformed array literal: "af_repo_app"
LINE 1: select _sa_setup_role('af_repo_app');
                              ^
DETAIL:  Array value must start with "{" or dimension information.

So ... any chance you have a data type named _sa_setup_role?

			regards, tom lane