public inbox for [email protected]
help / color / mirror / Atom feedFrom: Rumpi Gravenstein <[email protected]>
To: Tom Lane <[email protected]>
Cc: PostgreSQL <[email protected]>
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
Date: Fri, 25 Jul 2025 13:18:07 -0400
Message-ID: <CAEpg1wALRocK=uDSNyJqdc=vhNGjYFmT3H_TNzihSOMS88WHfg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAEpg1wBxp=25isxj6yt2cf97KtvbwxvJfrJ9qYF8UQxGSBJ93Q@mail.gmail.com>
<[email protected]>
<CAEpg1wCDL+iYbG7ByjHcgfvJy7m3m-rDp-xKiYovvxeKTbG7iQ@mail.gmail.com>
<[email protected]>
<snip>
Now I'm wondering about stray entries in pg_cast. Also,
do you have any extensions loaded in that DB that aren't
in your other ones?
</snip>
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.
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.
On Fri, Jul 25, 2025 at 1:10 PM Tom Lane <[email protected]> wrote:
> Rumpi Gravenstein <[email protected]> writes:
> > No ... just one version:
>
> D'oh, actually this would have complained if there was more
> than one match, so that theory is wrong:
>
> > xxxx_pub_dev_2_db=# DROP FUNCTION if exists _sa_setup_role;
> > DROP FUNCTION
>
> Now I'm wondering about stray entries in pg_cast. Also,
> do you have any extensions loaded in that DB that aren't
> in your other ones?
>
> regards, tom lane
>
--
Rumpi Gravenstein
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
In-Reply-To: <CAEpg1wALRocK=uDSNyJqdc=vhNGjYFmT3H_TNzihSOMS88WHfg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox