[GENERAL] Question about shared_buffer cache behavior

In Postgres 9.5.1 with a shared_buffer cache of 7Gb, a SELECT from a single table that uses an index appears to read the table into the shared_buffer cache. Then, as many times as the exact same SELECT is repeated in the same session, it runs blazingly fast and doesn't even touch the disk. All

Re: [GENERAL] Question about shared_buffer cache behavior

On Friday, March 18, 2016 4:54 PM, Andreas Kretschmer wrote:  >  >  >> Paul Jones hat am 18. Marz 2016 um 21:24 geschrieben:  >>  >>   >> In Postgres 9.5.1 with a shared_buffer cache of 7Gb, a SELECT from  >  > the first query reads only the tuple

Re: [GENERAL] Question about shared_buffer cache behavior

> Paul Jones hat am 18. März 2016 um 21:24 geschrieben: > > > In Postgres 9.5.1 with a shared_buffer cache of 7Gb, a SELECT from > a single table that uses an index appears to read the table into the > shared_buffer cache. Then, as many times as the exact same SELECT is >

Re: [GENERAL] Question about shared_buffer cache behavior

PG loads data at the block level to shared_buffers. Most likely it is because the second sql selects different set of rows (from different blocks) than the first sql. On Fri, Mar 18, 2016 at 4:24 PM, Paul Jones wrote: > In Postgres 9.5.1 with a shared_buffer cache of 7Gb, a