As Tom notes before maybe you're not using the right postgres. Solaris 10
comes with a postgres, but on SPARC it's 32 bit compiled (I can't speak to
x86 Solaris though).
Assuming that's not the problem, you can be 100% sure if your Postgres
binary is actually 64 bit by using the file command on the 'postgres'
executable. A sample from 64 bit SPARC looks like this:
postgres: ELF 64-bit MSB executable SPARCV9 Version 1, UltraSPARC3
Extensions Required, dynamically linked, not stripped
But x86 should show something similar. I have run Postgres up to about 8
gigs of RAM on Solaris without trouble. Anyway, sorry if this is obvious /
not helpful but good luck :)
On Tue, Jul 15, 2008 at 10:25 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Uwe Bartels" <uwe(dot)bartels(at)gmail(dot)com> writes:
> > When trying to to set shared_buffers greater then 3,5 GB on 32 GB x86
> > machine with solaris 10 I running in this error:
> > FATAL: requested shared memory size overflows size_t
> > The solaris x86 ist 64-bit and the compiled postgres is as well 64-bit.
> Either it's not really a 64-bit build, or you made an error in your
> math. What did you try to set shared_buffers to, exactly? Did you
> increase any other parameters at the same time?
> regards, tom lane
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-performance by date
|Next:||From: Patrick Vachon||Date: 2008-07-16 21:37:58|
|Subject: Difference between 8.1 & 8.3|
|Previous:||From: Jeffrey Baker||Date: 2008-07-15 15:54:00|
|Subject: Re: 3ware vs Areca|