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: <CAEpg1wALRocK=uDSNyJqdc=vhNGjYFmT3H_TNzihSOMS88WHfg@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>
Comments: In-reply-to Rumpi Gravenstein <rgravens@gmail.com>
	message dated "Fri, 25 Jul 2025 13:18:07 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1940679.1753465819.1@sss.pgh.pa.us>
Date: Fri, 25 Jul 2025 13:50:19 -0400
Message-ID: <1940680.1753465819@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1940680.1753465819%40sss.pgh.pa.us>
Precedence: bulk

Rumpi Gravenstein <rgravens@gmail.com> writes:
> Our databases are deployed with automation tools.  They should all be
> created the same.  They all have the same 17 extensions.  I've asked a DBA
> to confirm.

Well, there's got to be *something* different about that database.

> This issue only appears in the function I have listed.  A similar function,
> same contents and parameter but with a different name, works the way I
> would expect.

That sure seems like evidence in favor of the similarly-named-function
idea.  But I don't see how the DROP FUNCTION wouldn't have failed if
there were two, nor why we wouldn't see it in \df.

			regards, tom lane