From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ERROR: argument to pg_get_expr() must come from system catalogs |
Date: | 2010-07-13 15:44:10 |
Message-ID: | AANLkTilvhUk6MdMV9-RjoF2YViHaTG5iG3Kd6XAgyDhq@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13 July 2010 16:31, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> We had a report of the above error from a pgAdmin user testing
> 1.12.0b3 with PG 9.0b3. The (highly simplified) query below works fine
> as a superuser:
>
> SELECT pg_get_expr(proargdefaults, 'pg_catalog.pg_class'::regclass)
> FROM pg_proc pr
> LEFT OUTER JOIN pg_description des ON des.objoid=pr.oid
>
> Run as a regular user though, we get the error. If I remove the join,
> it works fine as the normal user. This is in a database owned by the
> regular user.
>
> Am I missing something obvious, or is there a bug here? pg_get_expr is
> used pretty extensively in pgAdmin, so we're obviously keen to ensure
> it works :-)
>
I tested this on both beta2 and beta3 and can confirm that it works on
beta2 but produces the following error in beta3:
********** Error **********
ERROR: argument to pg_get_expr() must come from system catalogs
SQL state: 42501
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-07-13 15:48:40 | Re: ERROR: argument to pg_get_expr() must come from system catalogs |
Previous Message | Dave Page | 2010-07-13 15:31:56 | ERROR: argument to pg_get_expr() must come from system catalogs |