Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.9, 4.0.3, WT3.2.0
Affects Version/s: None
Component/s: None
Labels:
- data-corruption

Sprint:
Storage Engines 2018-08-13, Storage Engines 2018-08-27, Storage Engines 2018-09-10
Story Points:
None

Backport Requested:

v4.0, v3.6

In local testing we saw a failure from test/format regards an unexpected value being returned after a WT_CURSOR::modify operation.

The failure is similar to those seen in ~~WT-4193~~, but now that the modify API has been changed to disallow modify in implicit transactions, there isn't an obvious cause.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

c4243
Aug 21 2018 05:56:55 AM UTC
1 kB
Alexander Gorrod
wt-4243-diag.diff
Aug 21 2018 05:56:24 AM UTC
4 kB
Alexander Gorrod

causes

WT-4300 Setting the update timestamp can overwrite the WT_REF.addr field

Closed

WT-4303 Performance regression on btree load time

Closed

is duplicated by

WT-4303 Performance regression on btree load time

Closed

is related to

WT-4193 Make WT_CURSOR.modify require explicit transactions

Closed

Assignee:: Alexander Gorrod
Reporter:: Alexander Gorrod
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Aug 09 2018 11:07:50 PM UTC
Updated:: Oct 29 2023 04:46:27 PM UTC
Resolved:: Sep 07 2018 05:53:38 AM UTC

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates