pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Fabrício dos Anjos Silva <fabricio.silva@linkcom.com.br>
To: pgsql-performance@postgresql.org
Subject: Re: How does PG know if data is in memory?
Date: Wed, 29 Sep 2010 11:36:45 -0500
Message-ID: <4CA324CD0200002500036117@gw.wicourts.gov> (raw)
In-Reply-To: <AANLkTin5G0jXUbeNdC+1s9LQpk1ZpvDuX-6n90oonen3@mail.gmail.com>
References: <AANLkTin5G0jXUbeNdC+1s9LQpk1ZpvDuX-6n90oonen3@mail.gmail.com>

Fabrício dos Anjos Silva<fabricio.silva@linkcom.com.br> wrote:
 
> After reading lots of documentation, I still don't understand
> fully how PG knows if some needed data is in memory or in second
> storage.
 
> Does PG consider this?
 
No.
 
> When setting seq_page_cost and random_page_cost, do I have to
> consider the probability that data will be in memory?
 
Yes.
 
-Kevin



view thread (31+ messages)  latest in thread

Message-ID: <4CA324CD0200002500036117@gw.wicourts.gov>
Permalink:  ../4CA324CD0200002500036117@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4CA324CD0200002500036117@gw.wicourts.gov

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, fabricio.silva@linkcom.com.br
  Subject: Re: How does PG know if data is in memory?
  In-Reply-To: <4CA324CD0200002500036117@gw.wicourts.gov>
  References: <AANLkTin5G0jXUbeNdC+1s9LQpk1ZpvDuX-6n90oonen3@mail.gmail.com> <4CA324CD0200002500036117@gw.wicourts.gov>

* 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