DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=Yjuflp2qdI4yPL7zFLpR3kELXbj4qEEtoTCVT75E10wHrCmi57+6eyLv3q1Tp126a4h83QhBnkXC8vEdoQyoskHbjXSZnery/PXnMFkL226WeMRJOlshSZ6ye1sBx/6FfccA0/TF7HJIrdp3jOPUAXrGvLfKVkCcARmC9Yb2Kec=
Message-ID: <1d219a6f0601091054q70283291v9deba2cb3c7b8fe@mail.gmail.com>
Date: Mon, 9 Jan 2006 13:54:48 -0500
From: Chris Hoover <revoohc@gmail.com>
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>,
	pgsql-performance@postgresql.org
Subject: Memory Usage Question
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_84319_23632822.1136832888923"

------=_Part_84319_23632822.1136832888923
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Question,

How exactly is Postgres and Linux use the memory?

I have serveral databases that have multi GB indexes on very large tables.
On our current servers, the indexes can fit into memory but not the data
(servers have 8 - 12 GB).  However, my boss is wanting to get new servers
for me but does not want to keep the memory requirements as high as they ar=
e
now (this will allow us to get more servers to spread our 200+ databases
over).

Question, if I have a 4GB+ index for a table on a server with 4GB ram, and =
I
submit a query that does an index scan, does Postgres read the entire index=
,
or just read the index until it finds the matching value (our extra large
indexes are primary keys).

I am looking for real number to give to my boss the say either having a
primary key larger than our memory is bad (and how to clearly justfify it),
or it is ok.

If it is ok, what are the trade offs in performance?\

Obviously, I want more memory, but I have to prove the need to my boss sinc=
e
it raises the cost of the servers a fair amount.

Thanks for any help,

Chris

------=_Part_84319_23632822.1136832888923
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Question,<br>
<br>
How exactly is Postgres and Linux use the memory?<br>
<br>
I have serveral databases that have multi GB indexes on very large
tables.&nbsp; On our current servers, the indexes can fit into memory
but not the data (servers have 8 - 12 GB).&nbsp; However, my boss is
wanting to get new servers for me but does not want to keep the memory
requirements as high as they are now (this will allow us to get more
servers to spread our 200+ databases over).<br>
<br>
Question, if I have a 4GB+ index for a table on a server with 4GB ram,
and I submit a query that does an index scan, does Postgres read the
entire index, or just read the index until it finds the matching value
(our extra large indexes are primary keys).<br>
<br>
I am looking for real number to give to my boss the say either having a
primary key larger than our memory is bad (and how to clearly justfify
it), or it is ok.<br>
<br>
If it is ok, what are the trade offs in performance?\<br>
<br>
Obviously, I want more memory, but I have to prove the need to my boss sinc=
e it raises the cost of the servers a fair amount.<br>
<br>
Thanks for any help,<br>
<br>
Chris<br>

------=_Part_84319_23632822.1136832888923--