PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
| От | David G. Johnston |
|---|---|
| Тема | PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array |
| Дата | |
| Msg-id | CAKFQuwZJJQz=Ap_S7taL1iJwS6tT0AvrVGThpxWMgQk9ZLSy2w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array (Rumpi Gravenstein <rgravens@gmail.com>) |
| Ответы |
Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
|
| Список | pgsql-general |
On Wednesday, August 6, 2025, Rumpi Gravenstein <rgravens@gmail.com> wrote:
xxx_pub_dev_2_db=# drop FUNCTION if exists _sa_setup_role;
DROP FUNCTION
xxx_pub_dev_2_db=# select proname, pronamespace, oid from pg_proc where proname like '%sa_setup%';
proname | pronamespace | oid
---------+--------------+-----
(0 rows)
xxx_pub_dev_2_db=# select _sa_setup_role('af_repo_app');
ERROR: malformed array literal: "af_repo_app"
LINE 1: select _sa_setup_role('af_repo_app');
^
DETAIL: Array value must start with "{" or dimension information.
xxx_pub_dev_2_db=#
Yeah, we’ve already pretty much decided this function has nothing to do with it. Go look at pg_type per the last example demonstrating the same error without the involvement of any user-defined function.
David J.
В списке pgsql-general по дате отправления: