Re: Getting fancy errors when accessing information_schema on 10.5

Axel Rau <Axel(dot)Rau(at)Chaos1(dot)DE> writes:
>> Am 30.10.2018 um 13:17 schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> It doesn't happen for me either. Looking at the planner code, it seems
>> like the relkind check should happen first because it'd be cheaper than
>> the OR condition. Have you perhaps messed with the cost attributed to
>> pg_has_role(), has_sequence_privilege(), or chareq()?

> Not by intention. The instance has some history, it go back to 8.x I think.

>> You could investigate with, eg,
>>
>> select oid::regprocedure, procost from pg_proc
>> where proname = 'has_sequence_privilege';

> nextcloud=> select oid::regprocedure, procost from pg_proc
> nextcloud-> where proname = 'has_sequence_privilege';
> oid | procost
> ----------------------------------------+---------
> has_sequence_privilege(name,text,text) | 1
> has_sequence_privilege(name,oid,text) | 1
> has_sequence_privilege(oid,text,text) | 1
> has_sequence_privilege(oid,oid,text) | 1
> has_sequence_privilege(text,text) | 1
> has_sequence_privilege(oid,text) | 1
> (6 rows)

Hm, nothing surprising there, but what about the other two?

regards, tom lane