Re: InitDB: Bad system call

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Torsten Zühlsdorff <foo(at)meisterderspiele(dot)de>
Cc: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: InitDB: Bad system call
Date: 2010-08-15 16:36:45
Message-ID: 21338.1281890205@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I wrote:
> ... The simplest explanation
> I can think of is that it's *only* shmctl that is malfunctioning, not
> the other SysV shared memory calls. Which is even weirder, and
> definitely seems to move the problem into the category of kernel bug
> rather than configuration mistake.

Hmmm ... Google turned up the information that FreeBSD migrated from int
to size_t variables for shared memory size between 7.0 and 8.0, and in
particular that the size of the struct used by shmctl() changed in
8.0. So I'm now wondering if what you're dealing with is some sort of
version skew problem. Could it be that you built Postgres against
system header files that don't match your kernel version? I'm not
exactly sure how that would manifest as this particular signal,
but it seems worth checking.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2010-08-16 05:34:01 Re: .psqlrc and custom functions (mysql-like)
Previous Message zhong ming wu 2010-08-15 16:22:35 Re: return setof : alternatives to holder table