Re: Getting fancy errors when accessing information_schema on 10.5 - Mailing list pgsql-admin

From Tom Lane
Subject Re: Getting fancy errors when accessing information_schema on 10.5
Date
Msg-id 29081.1540911887@sss.pgh.pa.us
Whole thread Raw
In response to Re: Getting fancy errors when accessing information_schema on 10.5  (Axel Rau <Axel.Rau@Chaos1.DE>)
Responses Re: Getting fancy errors when accessing information_schema on 10.5  (Axel Rau <Axel.Rau@chaos1.de>)
List pgsql-admin
Axel Rau <Axel.Rau@Chaos1.DE> writes:
> Am 30.10.2018 um 14:45 schrieb Tom Lane <tgl@sss.pgh.pa.us>:
>> Axel, would you try two more things on that DB?

> nextcloud=> explain select ((pg_has_role(relowner, 'USAGE'::text) OR has_sequence_privilege(oid, 'SELECT, UPDATE,
USAGE'::text)))from pg_class; 
>                         QUERY PLAN
> -----------------------------------------------------------
>  Seq Scan on pg_class  (cost=0.00..28.56 rows=656 width=1)
> (1 row)

> nextcloud=> explain select (relkind = 'S'::"char") from pg_class;
>                         QUERY PLAN
> -----------------------------------------------------------
>  Seq Scan on pg_class  (cost=0.00..28.56 rows=656 width=1)
> (1 row)

That is ... odd.  Is it possible that you have cpu_operator_cost set
to zero, or some very tiny number?

            regards, tom lane


pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Getting fancy errors when accessing information_schema on 10.5
Next
From: Axel Rau
Date:
Subject: Re: Getting fancy errors when accessing information_schema on 10.5