Sorry, been up all night and maybe provided too much information or not the right information and only confused folks, tired I guess. When I say 'in use' I am referring to the 'used' column. Thanks all who have responded to this inquiry, I appreciate it.
Here's free from PROD001:
[root@wbibsngwyprod001 kernel]# free -k -t
total used free shared buffers cached
Mem: 7643536 6975772 667764 0 165496 5393396
-/+ buffers/cache: 1416880 6226656
Swap: 8185108 5208 8179900
Total: 15828644 6980980 8847664
Here's free from PROD002:
[root@wbibsngwyprod002 root]# free -k -t
total used free shared buffers cached
Mem: 7643536 6694220 949316 0 161008 4916420
-/+ buffers/cache: 1616792 6026744
Swap: 8185108 11584 8173524
Total: 15828644 6705804 9122840
Tim
-----Original Message-----
From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Michael Stone
Sent: Friday, May 05, 2006 10:24 AM
To: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Memory and/or cache issues?
On Fri, May 05, 2006 at 09:57:58AM -0400, mcelroy, tim wrote:
>Are you saying the kernel's disc cache may be getting whacked? No, I
>understand that PG should use as much memory as it can and the system as
>well. The main problem here is that with almost all the 8GB of RAM 'in use'
>when I try to do a pg_dump or vacuumdb I run out of memory and the system
>crashes....
You need to be way more specific about what "in use" means. Try pasting
the output of actual commands like "free". The main problem here
according to the output you sent is that your process is trying to
allocate 10billion terabytes of RAM (which ain't gonna work) and dies.
That is not a memory issue.
Mike Stone
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
