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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rumpi Gravenstein <rgravens(at)gmail(dot)com>
Cc: 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-07-25 17:50:19
Message-ID: 1940680.1753465819@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Rumpi Gravenstein <rgravens(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2025-07-25 18:10:40 Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
Previous Message Rumpi Gravenstein 2025-07-25 17:18:07 Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array