Search Postgresql Archives

Re: enable_seqscan to off -> initial cost 10000000000

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 24 Apr 2021 at 03:44, Ron <ronljohnsonjr@xxxxxxxxx> wrote:
>
> On 4/23/21 10:39 AM, Luca Ferrari wrote:
> > Hi all,
> > this could be trivial, but I would like an explaination: if I turn off
> > sequential scans on a table without indexes, the same access plan is
> > increased by a 10000000000 factor. I suspect this is a warning for me
> > to remind that something is misconfigured, or is there anothe reason?
>
> Maybe I'm missing something, but in "a table without indexes", what else is
> there besides sequential scan?

You're not really missing anything.

However, technically, in the yet-to-be-released PG14, if the query had
a TID qual then you could disable seqscan to encourage a TID Range
scan. That's a bit of a stretch of the imagination though.

David





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux