| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: LIMIT not showing all results |
| Date: | 2019-03-05 18:44:05 |
| Message-ID: | d3fda33a-6ca3-01e9-7462-31ba0002ac7f@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 05.03.19 um 19:41 schrieb Casey Deccio:
>
>> On Mar 5, 2019, at 10:37 AM, Andreas Kretschmer
>> <andreas(at)a-kretschmer(dot)de <mailto:andreas(at)a-kretschmer(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-05 18:55:18 | Re: [External] LIMIT not showing all results |
| Previous Message | Andreas Kretschmer | 2019-03-05 18:43:18 | Re: [External] LIMIT not showing all results |