Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id A15AD65054D for ; Tue, 15 Jul 2008 18:53:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 39520-10 for ; Tue, 15 Jul 2008 18:53:39 -0300 (ADT) X-Greylist: delayed 00:20:23.286659 by SQLgrey-1.7.6 Received: from hs-out-0708.google.com (hs-out-0708.google.com [64.233.178.241]) by postgresql.org (Postfix) with ESMTP id E6D1C650084 for ; Tue, 15 Jul 2008 18:53:48 -0300 (ADT) Received: by hs-out-0708.google.com with SMTP id x43so1529572hsb.3 for ; Tue, 15 Jul 2008 14:53:47 -0700 (PDT) Received: by 10.100.119.12 with SMTP id r12mr382227anc.73.1216157212440; Tue, 15 Jul 2008 14:26:52 -0700 (PDT) Received: by 10.100.119.18 with HTTP; Tue, 15 Jul 2008 14:26:52 -0700 (PDT) Message-ID: <8752fe670807151426s3cab7a9dt49b8e180295bbda3@mail.gmail.com> Date: Tue, 15 Jul 2008 17:26:52 -0400 From: "Stephen Conley" To: "Uwe Bartels" , pgsql-performance@postgresql.org Subject: Re: requested shared memory size overflows size_t In-Reply-To: <18881.1216131953@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_12303_22241094.1216157212432" References: <8ea917510807150326l29c4d7e3g722623d6a7bea8d@mail.gmail.com> <18881.1216131953@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200807/135 X-Sequence-Number: 30735 ------=_Part_12303_22241094.1216157212432 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hey there; 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 :) Steve On Tue, Jul 15, 2008 at 10:25 AM, Tom Lane wrote: > "Uwe Bartels" 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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > ------=_Part_12303_22241094.1216157212432 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hey there;

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 :)

Steve

On Tue, Jul 15, 2008 at 10:25 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Uwe Bartels" <uwe.bartels@gmail.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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

------=_Part_12303_22241094.1216157212432--