MIME-Version: 1.0
In-Reply-To: <CAEpg1wBUcKjbM+vqP=JLHQUCOW9ct=aVRo1gBEtAZ5SuMY6cYQ@mail.gmail.com>
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> <1943137.1753467040@sss.pgh.pa.us>
 <c6d327b17ba73a17d455e88ef002ebbd242f87ab.camel@cybertec.at>
 <2223785.1753476729@sss.pgh.pa.us> <CAEpg1wBUcKjbM+vqP=JLHQUCOW9ct=aVRo1gBEtAZ5SuMY6cYQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 6 Aug 2025 13:43:22 -0700
Message-ID: <CAKFQuwZJJQz=Ap_S7taL1iJwS6tT0AvrVGThpxWMgQk9ZLSy2w@mail.gmail.com>
Subject: PostgreSQL Bug with simple function unexpectedly treating varchar
 parameter as an array
To: Rumpi Gravenstein <rgravens@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Laurenz Albe <laurenz.albe@cybertec.at>, 
	PostgreSQL <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000004ed0ba063bb8644b"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwZJJQz%3DAp_S7taL1iJwS6tT0AvrVGThpxWMgQk9ZLSy2w%40mail.gmail.com>
Precedence: bulk

--0000000000004ed0ba063bb8644b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, August 6, 2025, Rumpi Gravenstein <rgravens@gmail.com> wrote:

>
> xxx_pub_dev_2_db=3D# drop FUNCTION if exists _sa_setup_role;
> DROP FUNCTION
> xxx_pub_dev_2_db=3D# select proname, pronamespace, oid from pg_proc where
> proname like '%sa_setup%';
> proname | pronamespace | oid
> ---------+--------------+-----
> (0 rows)
>
> xxx_pub_dev_2_db=3D# 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.
> xxx_pub_dev_2_db=3D#
>

Yeah, we=E2=80=99ve already pretty much decided this function has nothing t=
o do
with it.  Go look at pg_type per the last example demonstrating the same
error without the involvement of any user-defined function.

David J.

--0000000000004ed0ba063bb8644b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, August 6, 2025, Rumpi Gravenstein &lt;<a href=3D"mailto:rgrav=
ens@gmail.com" target=3D"_blank">rgravens@gmail.com</a>&gt; wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"ltr"><br>xxx_pub_dev_2_db=3D# drop FU=
NCTION if exists _sa_setup_role;<br>DROP FUNCTION<br>xxx_pub_dev_2_db=3D# s=
elect proname, pronamespace, oid from pg_proc where proname like &#39;%sa_s=
etup%&#39;;<br>proname | pronamespace | oid<br>---------+--------------+---=
--<br>(0 rows)<br>=C2=A0<br>xxx_pub_dev_2_db=3D# select _sa_setup_role(&#39=
;af_repo_app&#39;);<br>ERROR: =C2=A0malformed array literal: &quot;af_repo_=
app&quot;<br>LINE 1: select _sa_setup_role(&#39;af_repo_app&#39;);<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 ^<br>DETAIL: =C2=A0Array value must start with =
&quot;{&quot; or dimension information.<br>xxx_pub_dev_2_db=3D#</div></bloc=
kquote><div><br></div><div>Yeah, we=E2=80=99ve already pretty much decided =
this function has nothing to do with it.=C2=A0 Go look at pg_type per the l=
ast example demonstrating the same error without the involvement of any use=
r-defined function.</div><div><br></div><div>David J.</div><div><br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"><div dir=3D"ltr" class=3D"gmail_signature"><i=
nput type=3D"hidden"><input type=3D"hidden"><div></div></div>
</blockquote>

--0000000000004ed0ba063bb8644b--