| From: | Axel Rau <Axel(dot)Rau(at)chaos1(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Getting fancy errors when accessing information_schema on 10.5 |
| Date: | 2018-10-30 15:51:00 |
| Message-ID: | 5208D6E1-0745-4C61-A324-73522EAF4BA1@Chaos1.DE |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
> Am 30.10.2018 um 16:29 schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> Axel Rau <Axel(dot)Rau(at)chaos1(dot)de> writes:
>>> Am 30.10.2018 um 16:04 schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lalith Tenneti | 2018-10-31 00:28:56 | ALTER PUBLICATION |
| Previous Message | Tom Lane | 2018-10-30 15:29:17 | Re: Getting fancy errors when accessing information_schema on 10.5 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-10-30 15:59:21 | Re: More issues with pg_verify_checksums and checksum verification in base backups |
| Previous Message | Patrick Francelle | 2018-10-30 15:50:13 | Re: Constraint documentation |