Horton

Re: Getting fancy errors when accessing information_schema on 10.5

Axel Rau <axel.rau@chaos1.de>

View thread View on postgr.es
From: Axel Rau <Axel.Rau@chaos1.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-admin@postgresql.org, pgsql-hackers@lists.postgresql.org
Date: 2018-10-30T15:51:00Z
Lists: pgsql-hackers 

> Am 30.10.2018 um 16:29 schrieb Tom Lane <tgl@sss.pgh.pa.us>:
> 
> Axel Rau <Axel.Rau@chaos1.de> writes:
>>> Am 30.10.2018 um 16:04 schrieb Tom Lane <tgl@sss.pgh.pa.us>:
>>> 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

I increased that value and the issue disappeared. (-:

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