[
https://issues.apache.org/jira/browse/COUCHDB-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116108#comment-13116108
]
Paul Joseph Davis commented on COUCHDB-1265:
--------------------------------------------
Really fixed in:
trunk r1176701
1.2.x r1176703
1.1.x r1176704
As a follow up to COUCHDB-1265 I was missing the fact that after the
insertion of a new update_seq into an internal node it is quite possible
that a compaction runs before the doc is updated again. This is
important because compaction removes information of the largest update
seq from the tree itself.
The fix is simple to include the update_seq from the #full_doc_info{}
record when calculating #doc_info.high_seq. The way to think of this
is that it's the maximum value from all known values for the update
sequence which can be defined as all values known in the tree or in the
full_doc_info record.
> Replication can introduce duplicates into the seq_btree.
> --------------------------------------------------------
>
> Key: COUCHDB-1265
> URL: https://issues.apache.org/jira/browse/COUCHDB-1265
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Reporter: Paul Joseph Davis
> Assignee: Paul Joseph Davis
> Fix For: 1.1.1, 1.2
>
> Attachments: COUCHDB-1265.patch, replication-frenzy.py
>
>
> Full description, test, and patch to follow shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
