Re: pgsql: Allow SetHintBits() to succeed if the buffer's LSN is new enough

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Allow SetHintBits() to succeed if the buffer's LSN is new enough
Date: 2016-02-15 22:19:32
Message-ID: CAM3SWZTreZ7MYCVZJ=Q2NLEVZOYqheTTYKK-71XeJGo6VU_ENw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Feb 15, 2016 at 2:17 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2016-02-15 22:01:12 +0000, Andres Freund wrote:
>> Allow SetHintBits() to succeed if the buffer's LSN is new enough.
>
> Thanks, that works with my brand of annoying compiler...

Wrong commit message. :-)

--
Peter Geoghegan

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2016-02-15 22:23:57 Re: pgsql: Suppress compiler warnings about useless comparison of unsigned
Previous Message Andres Freund 2016-02-15 22:17:09 Re: pgsql: Allow SetHintBits() to succeed if the buffer's LSN is new enough