From: Pierre C <lists@peufeu.com>
To: FabrÃcio dos Anjos Silva <fabricio.silva@linkcom.com.br>
To: Craig Ringer <craig@postnewspapers.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: How does PG know if data is in memory?
Date: Fri, 01 Oct 2010 15:45:34 +0200
Message-ID: <op.vjwgh8ejeorkce@apollo13> (raw)
In-Reply-To: <4CA5D2F5.5070900@postnewspapers.com.au>
References: <AANLkTin5G0jXUbeNdC+1s9LQpk1ZpvDuX-6n90oonen3@mail.gmail.com>
<AANLkTik5hnOcU=spN0wmWmR6_wHN=sKfVNzJeDuPTVW_@mail.gmail.com>
<AANLkTinrtVbjtadteR88xWGGYovAzhgOWR1=pXLDi08M@mail.gmail.com>
<4CA5D2F5.5070900@postnewspapers.com.au>
> It sounds horrendously complicated to keep track of to me, and in the
> end it won't make query execution any faster, it'll just potentially
> help the planner pick a better plan. I wonder if that'd be worth the
> extra CPU time spent managing the cache and cache content stats, and
> using those cache stats when planning? It'd be an interesting
> experiment, but the outcome is hardly obvious.
Well, suppose you pick an index scan, the only way to know which index
(and heap) pages you'll need is to actually do the index scan... which
isn't really something you'd do when planning. So you scan,
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: pgsql-performance@postgresql.org
Cc: lists@peufeu.com, fabricio.silva@linkcom.com.br, craig@postnewspapers.com.au
Subject: Re: How does PG know if data is in memory?
In-Reply-To: <op.vjwgh8ejeorkce@apollo13>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox