> On Mar 5, 2019, at 11:55 AM, Tom Lane wrote:
>
> Matthew Pounsett writes:
>> On Tue, 5 Mar 2019 at 12:54, Tom Lane wrote:
>>> Given that (a) this was triggered by a server migration and (b)
>>> the leading column of the index looks like it's probably varchar,
>>> I'm suspicious that the ne
> On Mar 5, 2019, at 10:37 AM, Andreas Kretschmer
> 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) migh
> On Mar 5, 2019, at 9:15 AM, Vijaykumar Jain wrote:
>
> Can you run both the queries with
> “explain analyze select ” and paste the output.
dnsviz=> explain analyze select id,name,date from analysis where name = 'foo'
order by date desc limit 20;
Okay, the subject is a little misleading because of course LIMIT isn't supposed
to all results, but I've got an issue where LIMIT isn't showing the number of
results I would expect. For example:
mydb=> select id,name,date from analysis where name = 'foo' order by date desc
limit 3;
id |
