Re: [PATCH] Refactoring of LWLock tranches - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [PATCH] Refactoring of LWLock tranches
Date
Msg-id 20160105161218.GF31334@momjian.us
Whole thread Raw
In response to Re: [PATCH] Refactoring of LWLock tranches  ("andres@anarazel.de" <andres@anarazel.de>)
List pgsql-hackers
On Tue, Jan  5, 2016 at 04:53:26PM +0100, Andres Freund wrote:
> On 2016-01-05 10:48:43 -0500, Bruce Momjian wrote:
> > On Tue, Jan  5, 2016 at 04:42:24PM +0100, Andres Freund wrote:
> > > On 2016-01-05 10:40:13 -0500, Bruce Momjian wrote:
> > > > On Tue, Jan  5, 2016 at 04:31:15PM +0100, Andres Freund wrote:
> > > > > On 2016-01-05 10:28:25 -0500, Bruce Momjian wrote:
> > > > > Yes? But it's ok sizewise on the common platforms?
> > > > 
> > > > What is the uncommon part?  I guess I missed that.
> > > 
> > > http://archives.postgresql.org/message-id/20151212181702.GH17938%40alap3.anarazel.de
> > 
> > Yes, I saw that, and the URL in the email, but what is the uncommon
> > case?
> 
> Are you asking which platforms s_lock is larger than a char? If so, grep
> s_lock.h for typedefs. If not, I'm not following what you're asking for?

Yes, that is the information I was looing for.  I see s_lock defined as
int-sized on Itanium, ARM, PowerPC, MIPS, m32r, PA-RISC, Windows,
Sunstudio.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription                             +



pgsql-hackers by date:

Previous
From: "andres@anarazel.de"
Date:
Subject: Re: [PATCH] Refactoring of LWLock tranches
Next
From: Tom Lane
Date:
Subject: Re: Making tab-complete.c easier to maintain