Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array - Mailing list pgsql-general

From Tom Lane
Subject Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
Date
Msg-id 1940680.1753465819@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array  (Rumpi Gravenstein <rgravens@gmail.com>)
Responses Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
List pgsql-general
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



pgsql-general by date:

Previous
From: Rumpi Gravenstein
Date:
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array