Subject: Re: Postgresql on an AMD64 machine
From: Mark Rinaudo <mark@bowmansystems.com>
To: postgres performance <pgsql-performance@postgresql.org>
Cc: tgl@sss.pgh.pa.us
In-Reply-To: <22887.1118092521@sss.pgh.pa.us>
References: <1118080420.1644.23.camel@penguin1>
	<b918cf3d05060613593a73a18a@mail.gmail.com>
	<22887.1118092521@sss.pgh.pa.us>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 06 Jun 2005 17:28:20 -0500
Message-Id: <1118096900.1893.58.camel@penguin1>
Mime-Version: 1.0

I'm running the Redhat Version of Postgresql which came pre-installed
with Redhat ES. It's version number is 7.3.10-1.  I'm not sure what
options it was compiled with. Is there a way for me to tell?  Should i
just compile my own postgresql for this platform?

Thanks
Mark

On Mon, 2005-06-06 at 16:15, Tom Lane wrote:
> Mike Rylander <mrylander@gmail.com> writes:
> > On 06 Jun 2005 12:53:40 -0500, Mark Rinaudo <mark@bowmansystems.com> wrote:
> >> I'm not sure if this is the appropriate list to post this question to
> >> but i'm starting with this one because it is related to the performance
> >> of Postgresql server.  I have a Penguin Computing dual AMD 64 bit
> >> opteron machine with 8 Gigs of memory.  In my attempt to increase the
> >> number of shared_buffers from the default to 65000 i was running into a
> >> semget error when trying to start Postgresql.
> 
> > Did you perhaps disable spinlocks when compiling PG?
> 
> That sure looks like it must be the issue --- in a normal build the
> number of semaphores needed does not vary with shared_buffers, but
> it will if Postgres is falling back to semaphore-based spinlocks.
> Which is a really bad idea from a performance standpoint, so you
> want to fix the build.
> 
> Which PG version is this exactly, and what configure options did
> you use?  What compiler was used?
> 
> 			regards, tom lane
> 
-- 
Mark Rinaudo
318-213-8780 ext 111
Bowman Systems