pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Very large caches (was Re: 7.3.1 New install, large queries are slow)
Date: 20 Jan 2003 03:41:21 -0600
Message-ID: <1043055681.15592.156.camel@haggis> (raw)
In-Reply-To: <27220.1043046883@sss.pgh.pa.us>
References: <web-2317350@davinci.ethosmedia.com>
	<3E2BE5DD.30158.D375D9A@localhost>
	<27220.1043046883@sss.pgh.pa.us>

On Mon, 2003-01-20 at 01:14, Tom Lane wrote:
> "Shridhar Daithankar" <shridhar_daithankar@persistent.co.in> writes:
> > On 17 Jan 2003 at 12:33, Tom Lane wrote:
[snip]
> > and that is also the only way to make postgresql use more than couple of gigs
> > of RAM, isn't it?
> 
> It seems quite unrelated.  The size of our shared memory segment is
> limited by INT_MAX --- chopping it up differently won't change that.
> 
> In any case, I think worrying because you can't push shared buffers
> above two gigs is completely wrongheaded, for the reasons already
> discussed in this thread.  The notion that Postgres can't use more
> than two gig because its shared memory is limited to that is
> *definitely* wrongheaded.  We can exploit however much memory your
> kernel can manage for kernel disk cache.

http://www.redhat.com/services/techsupport/production/GSS_caveat.html
"RAM Limitations on IA32
Red Hat Linux releases based on the 2.4 kernel -- including Red Hat
Linux 7.1, 7.2, 7.3 and Red Hat Linux Advanced Server 2.1 -- support
a maximum of 16GB of RAM."

So if I have some honking "big" Compaq Xeon SMP server w/ 16GB RAM,
and top(1) shows that there is 8GB of buffers, then Pg will be happy
as a pig in the mud?

-- 
+------------------------------------------------------------+
| Ron Johnson, Jr.     mailto:ron.l.johnson@cox.net          |
| Jefferson, LA  USA   http://members.cox.net/ron.l.johnson  |
|                                                            |
| "Basically, I got on the plane with a bomb. Basically, I   |
|  tried to ignite it. Basically, yeah, I intended to damage |
|  the plane."                                               |
|    RICHARD REID, who tried to blow up American Airlines    |
|                  Flight 63                                 |
+------------------------------------------------------------+




view thread (2+ messages)  latest in thread

Message-ID: <1043055681.15592.156.camel@haggis>
Permalink:  ../1043055681.15592.156.camel@haggis/
Also on:    postgresql.org/message-id/1043055681.15592.156.camel@haggis

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: ron.l.johnson@cox.net
  Subject: Re: Very large caches (was Re: 7.3.1 New install, large queries are slow)
  In-Reply-To: <1043055681.15592.156.camel@haggis>
  References: <web-2317350@davinci.ethosmedia.com> <3E2BE5DD.30158.D375D9A@localhost> <27220.1043046883@sss.pgh.pa.us> <1043055681.15592.156.camel@haggis>

* 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