Feedback-ID: i76984098:Fastmail
Message-ID: <5f2ce075-25f2-460e-8efc-0eec89afffca@aklaver.com>
Date: Wed, 6 Aug 2025 18:15:36 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar
 parameter as an array
To: Rumpi Gravenstein <rgravens@gmail.com>,
 "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>
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>
 <CAEpg1wCuZ5DgA_oj=pY8BUnsRP_7Lk24xXwjzp-Atw1-Uir-AA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAEpg1wCuZ5DgA_oj=pY8BUnsRP_7Lk24xXwjzp-Atw1-Uir-AA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/5f2ce075-25f2-460e-8efc-0eec89afffca%40aklaver.com>
Precedence: bulk

On 8/6/25 14:39, Rumpi Gravenstein wrote:
> That having a table and function with similar names causes this problem 
> is a bug.

Actually it is that a type and function have the same name. The 
connection is the table as that where the type gets it's name. Further 
complicated by you doing _type_name which turns the type into an array 
type.

Now that you know, as the old joke goes:

Doctor: What is the problem?
Patient: It hurts when I do this.
Doctor: Then don't do that.

:)

> 
> Going forward I'll be sure to avoid the problem.
> 
> On Wed, Aug 6, 2025 at 5:35 PM David G. Johnston 
> <david.g.johnston@gmail.com <mailto:david.g.johnston@gmail.com>> wrote:
> 
>     On Wednesday, August 6, 2025, Rumpi Gravenstein <rgravens@gmail.com
>     <mailto: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’t do that.  Naming a function (action) and table (noun) the same
>     seems unwise anyway, underscores or no.
> 
>     David J.
> 
> 
> 
> -- 
> Rumpi Gravenstein


-- 
Adrian Klaver
adrian.klaver@aklaver.com