Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Rumpi Gravenstein <rgravens(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
Date: 2025-08-06 21:35:24
Message-ID: CAKFQuwbU+xEmPdPvnvknz==yX5xLG5DuAxJASnPEcb73+WMATg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday, August 6, 2025, Rumpi Gravenstein <rgravens(at)gmail(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rumpi Gravenstein 2025-08-06 21:39:33 Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
Previous Message Rumpi Gravenstein 2025-08-06 21:29:26 Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array