Kevin Schroeder wrote:
Ignoring the fact that the sort and vacuum numbers are really high, this
is what Solaris shows me when running top:
Memory: 2048M real, 1376M free, 491M swap in use, 2955M swap free
Maybe check the swap usage with 'swap -l' which reports reliably if any
(device or file) sw
Hello,
I'm running PostgreSQL on a Solaris 8 system with 2GB of RAM and I'm
having some difficulty getting PostgreSQL to use the available RAM. My RAM
settings in postgresql.conf are
shared_buffers = 8192 # min 16, at least max_connections*2, 8KB each
sort_mem = 131072 # min
Benjamin,
> I just wanted to bounce off the list the best way to configure disks for a
> postgresql server. My gut feeling is as follows:
>
> Keep the OS and postgresql install on seperate disks to the postgresql
> /data directory?
> Is a single hard disk drive acceptable for the OS and postgresql
I just wanted to
bounce off the list the best way to configure disks for a postgresql server.
My gut
feeling is as follows:
Keep the OS and
postgresql install on seperate disks to the postgresql /data
directory?
Is a single hard
disk drive acceptable for the OS and postgresql program, or
Hi,
I try it and it doesn't resolve the problem:(
So, now what? To leave it that way for this query or There must be
permanent solution because if other queries behave like that?
Kaloyan Iliev
Tom Lane wrote:
Kaloyan Iliev Iliev <[EMAIL PROTECTED]> writes:
Will ANALYZE res
This must be a linux'ism because to my knowledge FreeBSD does not keep the
os-cache mapped into the kernel address space unless it have active objects
associated with the data.
And FreeBSD also have a default split of 3GB userspace and 1GB. kernelspace
when running with a default configuration.
Why dont you just grab the latest stable kernel from kernel.org,
customize it, compile it and the see what happens?
On Tue, 18 Jan 2005 09:35:12 +0700, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> > I understand that the 2.6.* kernels are much better at large memory
> > support (with respect to