From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200206080253.g582r6r23084@candle.pha.pa.us>
Subject: Re: [HACKERS] PostgreSQL on AIX
In-Reply-To: <46C15C39FEB2C44BA555E356FBCD6FA4961DF4@m0114.s-mxs.net>
To: Zeugswetter Andreas SB SD <ZeugswetterA@spardat.at>
Date: Fri, 7 Jun 2002 22:53:06 -0400 (EDT)
Cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Zeugswetter Andreas SB SD wrote:
> 
> > Anyway, I am pretty sure that PostgreSQL is not the culprit here.  As it 
> > happens this project is back on the table for me so it is interesting that 
> > your email popped up now.  I just compiled the latest version of PostgreSQL 
> > on my AIX system and it generated lots of errors and then completed and 
> > installed fine.  Makes me sort of nervous.  We'll see how it goes.  Anyone 
> > have any horror/success stories about PostgreSQL on AIX for me?
> 
> The "errors" are mostly duplicate symbol warnings, that are part of generating
> a shared lib on AIX (in a mostly gcc and xlc independent way), and can be safely
> ignored.
> 
> The imho most needed effort for AIX would be to switch the TAS stuff from
> cs() to fetch_and_or() or a PowerPC assembler or the test_and_set() that is 
> undocumented/intended for kernel, see discussions from last year.

Yes, TODO has:

	* Evaluate AIX cs() spinlock macro for performance optimizations (Tatsuo)

> The fetch_and_or() is a lot faster on multi processor systems but a little
> slower on single processor. But cs() is documented as depricated, so ...

Should I update the TODO item?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026