From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: fabricio.silva@linkcom.com.br, "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 10:40:11 -0400
Message-ID: <12383.1285944011@sss.pgh.pa.us> (raw)
In-Reply-To: <4CA59FCF02000025000362AE@gw.wicourts.gov>
References: <AANLkTin5G0jXUbeNdC+1s9LQpk1ZpvDuX-6n90oonen3@mail.gmail.com>
<AANLkTik5hnOcU=spN0wmWmR6_wHN=sKfVNzJeDuPTVW_@mail.gmail.com>
<AANLkTinrtVbjtadteR88xWGGYovAzhgOWR1=pXLDi08M@mail.gmail.com>
<4CA5D2F5.5070900@postnewspapers.com.au>
<4CA59FCF02000025000362AE@gw.wicourts.gov>
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> I agree with that, but I think there's an even more insidious issue
> here. Biasing plans heavily toward using what is already in cache
> could have a destabilizing effect on performance.
Not to mention the destabilizing effect on the plans themselves.
Behavior like that would make EXPLAIN nearly useless, because the plan
you get would vary from moment to moment even when "nothing is
changing". It's fairly clear that people don't actually want that.
regards, tom lane
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: tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov, craig@postnewspapers.com.au
Subject: Re: How does PG know if data is in memory?
In-Reply-To: <12383.1285944011@sss.pgh.pa.us>
* 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