From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Axel Rau <Axel(dot)Rau(at)Chaos1(dot)DE> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Getting fancy errors when accessing information_schema on 10.5 |
Date: | 2018-10-30 15:04:47 |
Message-ID: | 29081.1540911887@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Axel Rau <Axel(dot)Rau(at)Chaos1(dot)DE> writes:
> Am 30.10.2018 um 14:45 schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Axel Rau | 2018-10-30 15:12:32 | Re: Getting fancy errors when accessing information_schema on 10.5 |
Previous Message | Laurenz Albe | 2018-10-30 14:40:34 | Re: Getting fancy errors when accessing information_schema on 10.5 |
From | Date | Subject | |
---|---|---|---|
Next Message | Axel Rau | 2018-10-30 15:12:32 | Re: Getting fancy errors when accessing information_schema on 10.5 |
Previous Message | Peter Geoghegan | 2018-10-30 14:55:17 | PSA: rr recorder/debugger works well with Postgres + Linux |