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

Re: BUG #1549: initdb doesn't work

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Daniel van Eeden <daniel_e(at)dds(dot)nl>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1549: initdb doesn't work
Date: 2005-03-18 17:41:56
Message-ID: 8977.1111167716@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Daniel van Eeden wrote:
>> creating template1 database in /opt/postgresql/data/base/1 ... FATAL: 
>> semctl(10977333, 16, SETVAL, 536) failed: Invalid argument

> That is a problem with semaphores in your kernel.  Have you modified
> your postgresql.conf from the default?  If so, you should read the
> PostgreSQL documentation on how to modify your kernel for larger
> settings.

But it's failing at semctl() not semget().  So it seems he hasn't run
out of semaphores.  I wonder if SEMVMX is unusually small on his setup
(ie, less than 536).  My Linux semctl man page says that that case would
return ERANGE not EINVAL, but ...

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Brian O'ReillyDate: 2005-03-18 23:21:02
Subject: BUG #1552: massive performance hit between 7.4 and 8.0.1
Previous:From: Oliver SiegmarDate: 2005-03-18 17:35:10
Subject: {Spam?} Re: Possible temp table bug in PostgreSQL 7.4.7 / 8.0.1

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