Re: s_lock.h default definitions are rather confused - Mailing list pgsql-hackers

From andres@anarazel.de (Andres Freund)
Subject Re: s_lock.h default definitions are rather confused
Date
Msg-id 20150115123411.GD5245@awork2.anarazel.de
Whole thread Raw
In response to Re: s_lock.h default definitions are rather confused  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: s_lock.h default definitions are rather confused
List pgsql-hackers
On 2015-01-14 19:31:18 -0500, Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
> > Right now I think a #ifdef/undef S_UNLOCK in the relevant gcc section
> > sufficient and acceptable. It's after all the HPPA section that doesn't
> > really play by the rules.
> 
> Works for me.

Pushed something like that. Gaur has the note 'Runs infrequently' - I'm
not sure whether that means we'll see the results anytime soon...

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: M Tarkeshwar Rao
Date:
Subject: can you have any idea about toast missing chunk issu resolution
Next
From: Andres Freund
Date:
Subject: Re: Minor configure tweak to simplify adjusting gcc warnings