Am 05.03.19 um 19:41 schrieb Casey Deccio:
>
>> On Mar 5, 2019, at 10:37 AM, Andreas Kretschmer
>> <andreas@a-kretschmer.de <mailto:andreas@a-kretschmer.de>> wrote:
>>
>> no, but you can set enable_indexscan to off and maybe also
>> enable_bitmapscan to off to force the planner to choose a seq-scan.
>> I'm sure in this case you will get a correct result.
>
> So this (setting enable_indexscan to off) might be a short-term fix,
> while reindexing is the more robust fix?
>
yes, sure. The index is corrupt.
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com