Re: requested shared memory size overflows size_t

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Yuri Levinsky <yuril(at)celltick(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: requested shared memory size overflows size_t
Date: 2014-03-04 14:30:52
Message-ID: CA+Tgmoa2W+zyhJGQzML=hgn8i5iQP+PLJWnD5DX7NnCMS3a08A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 4, 2014 at 6:05 AM, Yuri Levinsky <yuril(at)celltick(dot)com> wrote:
> I changed postgresql.conf to decrease those parameters but no change: GMT54000FATAL: requested shared memory size overflows size_t

I think this means you are running on a 32-bit operating system, or at
least on a 32-bit build. That means you can't use more than 4GB of
address space per process, which has to fit shared_buffers and
everything else. Typically it's best not to set shared_buffers above
2-2.5GB on such systems, but the real solution is to use a 64-bit
PostgreSQL.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-03-04 14:47:08 Re: GSoC proposal - "make an unlogged table logged"
Previous Message Tom Lane 2014-03-04 14:26:45 Re: UNION ALL on partitioned tables won't use indices.