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 16:54:30
Message-ID: 1934172.1753462470@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:
> I've been confound by the following behavior that I see in one of our
> PostgreSQL 16 instances. In this case I am running this script from psql.

I'd bet there is another function named _sa_setup_role() that takes
some kind of array, and the parser is resolving the ambiguity by
choosing that one.

"\df _sa_setup_role" would be illuminating.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rumpi Gravenstein 2025-07-25 16:59:59 Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
Previous Message Adrian Klaver 2025-07-25 16:54:21 Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array