Received: from localhost (unknown [200.46.204.184])
	by developer.postgresql.org (Postfix) with ESMTP id 8A4D22E0053
	for <pgsql-performance-postgresql.org@developer.postgresql.org>;
	Thu,  3 Apr 2008 14:22:43 -0300 (ADT)
Received: from developer.postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024)
	with ESMTP id 58150-02
	for <pgsql-performance-postgresql.org@developer.postgresql.org>;
	Thu,  3 Apr 2008 14:22:37 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
Received: from mail.emproshunts.com (mail.emproshunts.com [66.64.191.19])
	by developer.postgresql.org (Postfix) with ESMTP id 98C792E0050
	for <pgsql-performance@postgresql.org>;
	Thu,  3 Apr 2008 14:22:38 -0300 (ADT)
Received: from [192.168.1.49] by mail.emproshunts.com (GMS
	15.00.3626/KX5895.00.ca7cb0e7) with ESMTP id cvyehaaa for
	pgsql-performance@postgresql.org; Thu, 3 Apr 2008 13:22:39 -0400
Message-ID: <47F52027.8070503@emproshunts.com>
Date: Thu, 03 Apr 2008 13:21:27 -0500
From: Justin <justin@emproshunts.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: [Fwd: Re: Max shared_buffers]
Content-Type: multipart/alternative;
	boundary="------------000802090904090201050309"
X-Originating-IP: [192.168.1.49]
X-DNSBL: 0
X-AntiSpam: Checked for restricted content by Gordano's AntiSpam Software
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200804/35
X-Sequence-Number: 29528

This is a multi-part message in MIME format.
--------------000802090904090201050309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Scott Marlowe wrote:
> On Thu, Apr 3, 2008 at 4:10 AM, sathiya psql <sathiya.psql@gmail.com> wrote:
>   
>> There is NO MAX....
>>
>> It is according to your hardware you have, and the db you have.
>>     
>
> Not entirely true.  on 32 bit OS / software, the limit is just under 2
> Gig.  I'd imagine that the limit on 64 bit hardware / software is
> therefore something around 2^63-somesmallnumber which is, for all
> practical purposes, unlimited.
>
>   
Its limited only by the hardware and OS you are running.    Some OS's on 
32bit allow for up to 4 gigs but you have to leave room for the OS and 
other running processes.  On 64 bit hardware it can be limited by the 
Hardware along with OS where its artificially limited to 32gigs, 64 gigs 
and 2TB  seem to be the most common limits set by the hardware or OS.   
But again you have to leave room in these setting for other processes if 
not out memory errors will occur and may crash the server.

In general these setting are only limited by the Hardware and OS

--------------000802090904090201050309
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<br>
Scott Marlowe wrote:
<blockquote
 cite="mid:dcc563d10804030949q64faad5ej2ca587faf4f5cae3@mail.gmail.com"
 type="cite">
  <pre wrap="">On Thu, Apr 3, 2008 at 4:10 AM, sathiya psql <a
 moz-do-not-send="true" class="moz-txt-link-rfc2396E"
 href="mailto:sathiya.psql@gmail.com">&lt;sathiya.psql@gmail.com&gt;</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">There is NO MAX....

It is according to your hardware you have, and the db you have.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Not entirely true.  on 32 bit OS / software, the limit is just under 2
Gig.  I'd imagine that the limit on 64 bit hardware / software is
therefore something around 2^63-somesmallnumber which is, for all
practical purposes, unlimited.

  </pre>
</blockquote>
Its limited only by the hardware and OS you are running.&nbsp;&nbsp;&nbsp; Some OS's
on 32bit allow for up to 4 gigs but you have to leave room for the OS
and other running processes.&nbsp; On 64 bit hardware it can be limited by
the Hardware along with OS where its artificially limited to 32gigs, 64
gigs and 2TB&nbsp; seem to be the most common limits set by the hardware or
OS.&nbsp;&nbsp; But again you have to leave room in these setting for other
processes if not out memory errors will occur and may crash the server.
<br>
<br>
In general these setting are only limited by the Hardware and OS <br>
</body>
</html>

--------------000802090904090201050309--