public inbox for [email protected]
help / color / mirror / Atom feedFrom: Rick Otten <[email protected]>
To: Artem Tomyuk <[email protected]>
Cc: [email protected]
Subject: Re: using shared_buffers during seq_scan
Date: Thu, 17 Mar 2016 09:07:08 -0400
Message-ID: <CAMAYy4KJXbpza61WyO1ssXTV-AnKU1d3xiBprbLc2uuwY1vTzg@mail.gmail.com> (raw)
In-Reply-To: <CANYYVqJsDJhGHCL=NPCsoQ5Sv7x_iWggF+p=VF7OASrjDun4DA@mail.gmail.com>
References: <CANYYVqJsDJhGHCL=NPCsoQ5Sv7x_iWggF+p=VF7OASrjDun4DA@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-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 <[email protected]> wrote:
> Hi All!
>
> Is Postgres use shared_buffers during seq_scan?
> In what way i can optimize seq_scan on big tables?
>
> Thanks!
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: using shared_buffers during seq_scan
In-Reply-To: <CAMAYy4KJXbpza61WyO1ssXTV-AnKU1d3xiBprbLc2uuwY1vTzg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox