pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Wiles <frank@wiles.org>
To: Guido Neitzer <lists@event-s.net>
Cc: Gopal <gopal@getmapping.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres scalability and performance on windows
Date: Fri, 24 Nov 2006 11:04:51 -0600
Message-ID: <20061124110451.4538d901.frank@wiles.org> (raw)
In-Reply-To: <A1ECB7A7-E6F7-495B-8563-E675EC49CBCB@event-s.net>
References: <A5DE6132B8D812419321747E42710E2204C05F@EXCHANGE01.gm.local>
	<A1ECB7A7-E6F7-495B-8563-E675EC49CBCB@event-s.net>

On Fri, 24 Nov 2006 09:22:45 +0100
Guido Neitzer <lists@event-s.net> wrote:

> > effective_cache_size = 82728                  # typically 8KB each
> Hmm. I don't know what the real effect of this might be as the doc  
> states:
> 
> "This parameter has no effect on the size of shared memory allocated  
> by PostgreSQL, nor does it reserve kernel disk cache; it is used
> only for estimation purposes."

   This is a hint to the optimizer about how much of the database may
   be in the OS level cache.  

 ---------------------------------
   Frank Wiles <frank@wiles.org>
   http://www.wiles.org
 ---------------------------------




view thread (9+ messages)  latest in thread

Message-ID: <20061124110451.4538d901.frank@wiles.org>
Permalink:  ../20061124110451.4538d901.frank@wiles.org/
Also on:    postgresql.org/message-id/20061124110451.4538d901.frank@wiles.org

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: frank@wiles.org, lists@event-s.net, gopal@getmapping.com
  Subject: Re: Postgres scalability and performance on windows
  In-Reply-To: <20061124110451.4538d901.frank@wiles.org>

* 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