Skip site navigation (1) Skip section navigation (2)

Re: Postgres errors in Drupal install.

From: Peter Bex <Peter(dot)Bex(at)xs4all(dot)nl>
To: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgres errors in Drupal install.
Date: 2011-06-26 21:30:45
Message-ID: 20110626213045.GC7153@frohike.homeunix.org (view raw or flat)
Thread:
Lists: pgsql-general
On Sun, Jun 26, 2011 at 11:23:30PM +0200, Dave Coventry wrote:
[snip]
> 2011-06-26 17:13:24 EDT DETAIL:  Failed system call was
> shmget(key=5432001, size=29278208, 03600).
> 2011-06-26 17:13:24 EDT HINT:  This error usually means that
> PostgreSQL's request for a shared memory segment exceeded available
> memory or swap space. To reduce the request size (currently 29278208
> bytes), reduce PostgreSQL's shared_buffers parameter (currently 3072)
> and/or its max_connections parameter (currently 103).
> 	The PostgreSQL documentation contains more information about shared
> memory configuration.

This sounds like you should tweak those parameters. See the relevant section:
http://www.postgresql.org/docs/current/interactive/kernel-resources.html#SYSVIPC

> While the server is a little challenged in the way of RAM, it is by no
> means under any sort of load.

Drupal is a huge memory hog.  It's quite possible that it consumes so
much memory that it doesn't leave enough for postgres.  If at all
possible, try increasing the amount of memory available.

Cheers,
Peter
-- 
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music."
							-- Donald Knuth

In response to

pgsql-general by date

Next:From: John R PierceDate: 2011-06-26 21:37:22
Subject: Re: Postgres errors in Drupal install.
Previous:From: Eduard-Cristian StefanDate: 2011-06-26 21:27:10
Subject: Re: Relative path specified for data_directory is not working as expected

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group