Re: PinBuffer() no longer makes use of strategy

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com>
Subject: Re: PinBuffer() no longer makes use of strategy
Date: 2017-02-23 21:20:44
Message-ID: 1b63bdb1-12ed-0b95-061e-ead68d3e0e4b@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nico Williams 2017-02-23 21:27:43 Re: Idea on how to simplify comparing two sets
Previous Message Jim Nasby 2017-02-23 21:16:07 Re: Idea on how to simplify comparing two sets