On July 26, 2018 10:03:39 AM PDT, Robert Haas <robertmhaas@gmail.com> wrote:
>On Tue, Jun 26, 2018 at 7:45 AM, Magnus Hagander <magnus@hagander.net>
>wrote:
>> PFA an updated version of the patch for the next CF. We believe this
>one
>> takes care of all the things pointed out so far.
>>
>> For this version, we "implemented" the
>MegaExpensiveRareMemoryBarrier() by
>> simply requiring a restart of PostgreSQL to initiate the conversion
>> background. That is definitely going to guarantee a memory barrier.
>It's
>> certainly not ideal, but restarting the cluster is still a *lot*
>better than
>> having to do the entire conversion offline. This can of course be
>improved
>> upon in the future, but for now we stuck to the safe way.
>
>Honestly, I feel like the bar for this feature ought to be higher than
>that.
>
>(I half-expect a vigorous discussion of whether I have set the bar for
>the features I've developed in the right place or not, but I think
>that's not really a fair response. If somebody thinks some feature I
>implemented should've been more baked, they might be right, but that's
>not what this thread is about. I'm giving you MY opinion about THIS
>patch, nothing more or less.)
+1
>Why can't we do better?
I don't think it's that hard to do better. IIRC I even outlined something before the freeze. If not, o certainly can
(sketch:use procsignal based acknowledgment protocol, using a 64 bit integer. Useful for plenty other things).
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
