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 16:25:53 |
Message-ID: | AANLkTikon9XY75hgx61MSzik0K6KsD1Y-KW7V6H1Ryqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13 July 2010 17:01, Thom Brown <thombrown(at)gmail(dot)com> wrote:
> On 13 July 2010 17:00, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> On Tue, Jul 13, 2010 at 4:56 PM, Thom Brown <thombrown(at)gmail(dot)com> wrote:
>>
>>> I works if you use pr.proargdefaults so not unresolvable. Maybe it's
>>> because it can't tell where the column's coming from at that point?
>>
>> Hmm, so it does. It still seems like a bug though - why should it be
>> able to resolve the column based on whether you're a superuser or not,
>> just because it's not qualified?
>>
>
> Yeah see what you mean. Seems like a bug.
>
> Thom
>
And yes, as a result PgAdmin becomes very upset when not a superuser.
:( Kind of a show-stopper.
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-07-13 18:14:25 | Re: explain.c: why trace PlanState and Plan trees separately? |
Previous Message | Thom Brown | 2010-07-13 16:01:37 | Re: ERROR: argument to pg_get_expr() must come from system catalogs |