On Tue, Jun 26, 2018 at 7:45 AM, Magnus Hagander <mag...@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.) Why can't we do better? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
