while you weren't looking, Francisco Reyes wrote:

> Is there any disadvantage of having the enable_seqscan off?


The planner will choose whichever plan looks "cheapest", based on the
information it has available (table size, statistics, &c).  If a
sequential scan looks cheaper, and in your case above it clearly is,
the planner will choose that query plan.  Setting enable_seqscan =
false doesn't actually disable sequential scans; it merely makes them
seem radically more expensive to the planner, in hopes of biasing its
choice towards another query plan.  In your case, that margin made an
index scan look less expensive than sequential scan, but your query
runtimes clearly suggest otherwise.

In general, it's best to let the planner make the appropriate choice
without any artificial constraints.  I've seen pathalogical cases
where the planner makes the wrong choice(s), but upon analysis,
they're almost always attributable to poor statistics, long
un-vacuumed tables, &c.



---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Reply via email to