Re: Rework the way multixact truncations work

<div dir="ltr">+1<br /></div><div class="gmail_extra"><br /><div class="gmail_quote">On Thu, Dec 10, 2015 at 9:58 AM,
PeterGeoghegan <span dir="ltr"><<a href="mailto:pg@heroku.com" target="_blank">pg@heroku.com</a>></span>
wrote:<br/><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">OnThu, Dec 10, 2015 at 12:34 AM, Andres Freund <<a
href="mailto:andres@anarazel.de">andres@anarazel.de</a>>wrote:<br /> >> > Ripping it out and replacing it
monolithicallywill not<br /> >> > change that; it will only make the detailed history harder to<br /> >>
>reconstruct, and I *will* want to reconstruct it.<br /> >><br /> >> What's something that might happen
sixmonths from now and lead you to inspect<br /> >> master or 9.5 multixact.c between 4f627f8 and its revert?<br
/>><br /> > "Hey, what has happened to multixact.c lately? I'm investigating a bug,<br /> > and I wonder if it
alreadyhas been fixed?", "Uh, what was the problem<br /> > with that earlier large commit?", "Hey, what has changed
betweenbeta2<br /> > and the final release?"...<br /><br /></span>Quite.<br /><br /> I can't believe we're still
havingthis silly discussion. Can we please move on?<br /><span class="HOEnZb"><font color="#888888"><br /> --<br />
PeterGeoghegan<br /></font></span><div class="HOEnZb"><div class="h5"><br /><br /> --<br /> Sent via pgsql-hackers
mailinglist (<a href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br /> To make changes to
yoursubscription:<br /><a href="http://www.postgresql.org/mailpref/pgsql-hackers" rel="noreferrer"
target="_blank">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/></div></div></blockquote></div><br /><br
clear="all"/><br />-- <br /><div class="gmail_signature">Bert Desmet<br />0477/305361</div></div>