Re: using shared_buffers during seq_scan - Mailing list pgsql-performance

From Rick Otten
Subject Re: using shared_buffers during seq_scan
Date
Msg-id CAMAYy4KJXbpza61WyO1ssXTV-AnKU1d3xiBprbLc2uuwY1vTzg@mail.gmail.com
Whole thread Raw
In response to using shared_buffers during seq_scan  (Artem Tomyuk <admin@leboutique.com>)
List pgsql-performance
There is parallel sequence scanning coming in 9.6 -- http://rhaas.blogspot.com/2015/11/parallel-sequential-scan-is-committed.html 

And there is the GPU extension - https://wiki.postgresql.org/wiki/PGStrom 

If those aren't options, you'll want your table as much in memory as possible so your scan doesn't have to to go disk.



On Thu, Mar 17, 2016 at 5:57 AM, Artem Tomyuk <admin@leboutique.com> wrote:
Hi All!

Is  Postgres use shared_buffers during seq_scan? 
In what way i can optimize seq_scan on big tables?

Thanks!

pgsql-performance by date:

Previous
From: Artem Tomyuk
Date:
Subject: using shared_buffers during seq_scan
Next
From: Tom Lane
Date:
Subject: Re: Searching GIN-index (FTS) and sort by timestamp-column