If I am looking for a solution to the problem, I do not care about the state of the thing months or years in the past, I want to know what the status is now. I admire the fact that you are diligently updating your answer, and that's great, but the best way to update the answer is to rewrite it to be up-to-date without just tacking stuff on at the bottom.
So right now you have the answer and two updates. It looks like, from what I've read, there is an explanation of the problem, a workaround, and it has finally been fixed in a recent (but unstable) version. I would write it much more simply as:
- This issue is caused by a bug in the code related to big tables
- This is fixed in version 0.12 (an unstable release right now)
- If you use an earlier version, you can try this workaround
This makes it easy for anyone who stumbles across the question to identify the cause, figure out the solution for their circumstance, and is a great answer. Keep up the good work!