From: | <pbj(at)cmicdo(dot)com> |
---|---|
To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, Paul Jones <pbj(at)cmicdo(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Question about shared_buffer cache behavior |
Date: | 2016-03-18 21:22:58 |
Message-ID: | 940176702.1184891.1458336178735.JavaMail.yahoo@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday, March 18, 2016 4:54 PM, Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>
wrote:
>
>
>> Paul Jones <pbj(at)cmicdo(dot)com> 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 from heap that are matched the
> where-condition.
> The 2nd query with an other where-condition reads other rows than the first
> query.
>
> Keep in mind: a index search reads the index and pulls the rows that matched
the
> condition from the heap, no more.
Ok, thanks! I understand now!
>
> Regards
> --
> Andreas Kretschmer
> http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2016-03-18 21:29:51 | Re: ON CONFLICT DO NOTHING RETURNING |
Previous Message | Rakesh Kumar | 2016-03-18 21:04:47 | Re: Question about shared_buffer cache behavior |