DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=FG0u6brXpPJyAiRnA5m+SEtaTHf128NbSYOyVB+dLManXWO34BkRwvQN+yfgReHS7icDZXb+gkIlJHZ8+JhKhV4ka4ocRpSOl3/FgBYqWR3nNXakqXJX2gnaVAXFDeQ9vG3hpcymcfCv1dVluRq7hrkDVvR5QpkPIBDJP0TSEb8=;
Message-ID: <994489.22729.qm@web39706.mail.mud.yahoo.com>
Date: Thu, 10 Jun 2010 07:41:15 -0700 (PDT)
From: Bob Lunney <bob_lunney@yahoo.com>
Subject: Re: requested shared memory size overflows size_t
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-performance@postgresql.org, Tom Wilcox <hungrytom@googlemail.com>
In-Reply-To: <AANLkTin9D34AnGHhiyjUtpWV_B7IaSctHdeHfTpqiipF@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

True, plus there are the other issues of increased checkpoint times and I/O=
, bgwriter tuning, etc.  It may be better to let the OS cache the files and=
 size shared_buffers to a smaller value.  =0A=0ABob Lunney=0A=0A--- On Wed,=
 6/9/10, Robert Haas <robertmhaas@gmail.com> wrote:=0A=0A> From: Robert Haa=
s <robertmhaas@gmail.com>=0A> Subject: Re: [PERFORM] requested shared memor=
y size overflows size_t=0A> To: "Bob Lunney" <bob_lunney@yahoo.com>=0A> Cc:=
 pgsql-performance@postgresql.org, "Tom Wilcox" <hungrytom@googlemail.com>=
=0A> Date: Wednesday, June 9, 2010, 9:49 PM=0A> On Wed, Jun 2, 2010 at 9:26=
 PM, Bob=0A> Lunney <bob_lunney@yahoo.com>=0A> wrote:=0A> > Your other opti=
on, of course, is a nice 64-bit linux=0A> variant, which won't have this pr=
oblem at all.=0A> =0A> Although, even there, I think I've heard that after =
10GB=0A> you don't get=0A> much benefit from raising it further.=A0 Not sur=
e if=0A> that's accurate or=0A> not...=0A> =0A> -- =0A> Robert Haas=0A> Ent=
erpriseDB: http://www.enterprisedb.com=0A> The Enterprise Postgres Company=
=0A> =0A=0A=0A