Re: Getting fancy errors when accessing information_schema on 10.5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Am 30.10.2018 um 16:04 schrieb Tom Lane <tgl@xxxxxxxxxxxxx>:

Axel Rau <Axel.Rau@xxxxxxxxx> writes:
Am 30.10.2018 um 14:45 schrieb Tom Lane <tgl@xxxxxxxxxxxxx>:
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?

Yes:

cpu_index_tuple_cost = 0.01
cpu_operator_cost = 0

effective_cache_size = 4GB

Axel
---
PGP-Key:29E99DD6  ☀  computing @ chaos claudius


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux