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:10:22
Message-ID: 1936547.1753463422@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:
> 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

In response to

Responses

Browse pgsql-general by date

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