MIME-Version: 1.0
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>
 <CAKFQuwZJJQz=Ap_S7taL1iJwS6tT0AvrVGThpxWMgQk9ZLSy2w@mail.gmail.com>
 <CAEpg1wA=sJ4Cvs3hUN9rfYBwTC74uFWYUzQGfcfZC4u-K1AH7w@mail.gmail.com> <CAKFQuwbU+xEmPdPvnvknz==yX5xLG5DuAxJASnPEcb73+WMATg@mail.gmail.com>
In-Reply-To: <CAKFQuwbU+xEmPdPvnvknz==yX5xLG5DuAxJASnPEcb73+WMATg@mail.gmail.com>
From: Rumpi Gravenstein <rgravens@gmail.com>
Date: Wed, 6 Aug 2025 17:39:33 -0400
Message-ID: <CAEpg1wCuZ5DgA_oj=pY8BUnsRP_7Lk24xXwjzp-Atw1-Uir-AA@mail.gmail.com>
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar
 parameter as an array
To: "David G. Johnston" <david.g.johnston@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="000000000000da122a063bb92d74"
Archived-At: <https://www.postgresql.org/message-id/CAEpg1wCuZ5DgA_oj%3DpY8BUnsRP_7Lk24xXwjzp-Atw1-Uir-AA%40mail.gmail.com>
Precedence: bulk

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

That having a table and function with similar names causes this problem is
a bug.

Going forward I'll be sure to avoid the problem.

On Wed, Aug 6, 2025 at 5:35=E2=80=AFPM David G. Johnston <david.g.johnston@=
gmail.com>
wrote:

> On Wednesday, August 6, 2025, Rumpi Gravenstein <rgravens@gmail.com>
> wrote:
>
>> Here's a reproducible test case that causes the problem in different
>> schemas.  The issue appears to be related to creating a table and a
>> function that has the same name as the table with a prepended underscore=
.
>>
>
> Don=E2=80=99t do that.  Naming a function (action) and table (noun) the s=
ame seems
> unwise anyway, underscores or no.
>
> David J.
>
>

--=20
Rumpi Gravenstein

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

<div dir=3D"ltr">That having a table and function with similar names causes=
 this problem is a bug.<div><br></div><div>Going forward I&#39;ll be sure t=
o avoid the problem.</div></div><br><div class=3D"gmail_quote gmail_quote_c=
ontainer"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Aug 6, 2025 at 5:35=
=E2=80=AFPM David G. Johnston &lt;<a href=3D"mailto:david.g.johnston@gmail.=
com">david.g.johnston@gmail.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">On Wednesday, August 6, 2025, Rumpi Graven=
stein &lt;<a href=3D"mailto:rgravens@gmail.com" target=3D"_blank">rgravens@=
gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div dir=3D"ltr">Here&#39;s a reproducible=C2=A0test case that causes th=
e problem=C2=A0in different schemas.=C2=A0 The issue appears to be related =
to creating a table and a function that has the same name as the table with=
 a prepended underscore.</div></blockquote><div><br></div><div>Don=E2=80=99=
t do that.=C2=A0 Naming a function (action) and table (noun) the same seems=
 unwise anyway, underscores or no.</div><div><br></div><div>David J.</div><=
div><br></div>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature">Rumpi Gravenstein<input type=3D"hidden"><input type=3D"hidden"><d=
iv></div></div>

--000000000000da122a063bb92d74--