Re: [HACKERS] PinBuffer() no longer makes use of strategy - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] PinBuffer() no longer makes use of strategy
Date
Msg-id 1b63bdb1-12ed-0b95-061e-ead68d3e0e4b@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] PinBuffer() no longer makes use of strategy  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
On 2/4/17 1:47 PM, Alexander Korotkov wrote:
>     I'm tempted to put the old logic back, but more because this likely was
>     unintentional, not because I think it's clearly better.
>
>
> +1
> Yes, it was unintentional change.  So we should put old logic back
> unless we have proof that this change make it better.
> Patch is attached.  I tried to make some comments, but probably they are
> not enough.

Added to CF: https://commitfest.postgresql.org/13/1029/
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] Idea on how to simplify comparing two sets
Next
From: Nico Williams
Date:
Subject: Re: [HACKERS] Idea on how to simplify comparing two sets