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 1936547.1753463422@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:
> 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



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: Rumpi Gravenstein
Date:
Subject: Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array