From: Neil Conway <neilc@samurai.com>
To: Paul Ramsey <pramsey@refractions.net>
Cc: Doug Y <dylists@ptd.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: The never ending quest for clarity on shared_buffers
Date: Thu, 07 Oct 2004 11:29:07 +1000
Message-ID: <1097112547.13119.108.camel@localhost.localdomain> (raw)
In-Reply-To: <41647127.3060407@refractions.net>
References: <6.1.2.0.2.20041006152747.033bcd50@pop.traderonline.com>
<41647127.3060407@refractions.net>
On Thu, 2004-10-07 at 08:26, Paul Ramsey wrote:
> The shared_buffers are shared (go figure) :). It is all one pool shared
> by all connections.
Yeah, I thought this was pretty clear. Doug, can you elaborate on where
you saw the misleading docs?
> The sort_mem and vacuum_mem are *per*connection* however, so when
> allocating that size you have to take into account your
> expected number of concurrent connections.
Allocations of size `sort_mem' can actually can actually happen several
times within a *single* connection (if the query plan happens to involve
a number of sort steps or hash tables) -- the limit is on the amount of
memory that will be used for a single sort/hash table. So choosing the
right figure is actually a little more complex than that.
-Neil
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: neilc@samurai.com, pramsey@refractions.net, dylists@ptd.net
Subject: Re: The never ending quest for clarity on shared_buffers
In-Reply-To: <1097112547.13119.108.camel@localhost.localdomain>
* 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