On Thu, 2005-05-12 at 12:46, Kavan, Dan (IMS) wrote:
> Do psql calls/procedures access resources reserved from the
> kernel.shmmax?
Only in the sense that it can execute a query, which in the backend
could therefore use shared memory. psql, itself, doesn't use shared
memory.
> How about the tar
gs up.
-Original Message-
From: Scott Marlowe [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 12, 2005 11:21 AM
To: Kavan, Dan (IMS)
Cc: postgres
Subject: RE: [ADMIN] memory allocation ; postgresql-8.0
On Thu, 2005-05-12 at 10:10, Kavan, Dan (IMS) wrote:
> Hi Scott,
>
> Thanks
On Thu, 2005-05-12 at 10:10, Kavan, Dan (IMS) wrote:
> Hi Scott,
>
> Thanks again for all your tips.
>
> If I knock the buffer size down to 65,536 (still higher than what you
> are recommending) then my shmmax becomes:
> 256,000 + 550,292,685 (65536*8396.8) + 1,454,100 = 552,002,785
>
> That
~DjK
-Original Message-
From: Scott Marlowe [mailto:[EMAIL PROTECTED]
Sent: Friday, May 06, 2005 3:31 PM
To: Kavan, Dan (IMS)
Subject: RE: [ADMIN] memory allocation ; postgresql-8.0
On Fri, 2005-05-06 at 14:12, Kavan, Dan (IMS) wrote:
> Unless you routinely actually handle data sets that
On Fri, 2005-05-06 at 13:28, Kavan, Dan (IMS) wrote:
> Hi,
>
> I am reserving 2.1 GB of memory for postgres to use with SuSE linux 9.0
> (SLES) in sysctl.conf.
> I have configured postgres to use 1.9 GB of memory so it won't go over
> the 2.1 cap (postgresql.conf).
> I have a total of 4GB of
