Hi there,
This is likely me not understanding something, but I have a query that
I would expect to be fast but PG insists on using a sequential scan.
I've attached a minimized test case but I'll walk through the steps as
well.
I'm running PostgreSQL 10.1 using the standard ArchLinux packages,
On Thu, Dec 1, 2022 at 8:21 PM Justin Pryzby wrote:
> Could you show explain analyze ?
>
> Maybe on both a well-behaving instance and a badly-beving instance.
Apologies for barging into this thread with a potentially unrelated
"me too" but here's a similar OR-causes-seqscan from 2018:
