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

2016-02-15 Thread Peter Geoghegan
On Mon, Feb 15, 2016 at 2:17 PM, Andres Freund wrote: > On 2016-02-15 22:01:12 +, 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 -- Sent v

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

2016-02-15 Thread Andres Freund
On 2016-02-15 22:01:12 +, Andres Freund wrote: > Allow SetHintBits() to succeed if the buffer's LSN is new enough. Thanks, that works with my brand of annoying compiler... Andres -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscriptio

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

2016-02-15 Thread Andres Freund
Allow SetHintBits() to succeed if the buffer's LSN is new enough. Previously we only allowed SetHintBits() to succeed if the commit LSN of the last transaction touching the page has already been flushed to disk. We can't generally change the LSN of the page, because we don't necessarily have the r