Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Fix Version/s: WT1.0
Affects Version/s: None
Component/s: None
Labels:
- Bug

Sprint:
None
Story Points:
None

It occurred to me – in the page-search code, we copy the page's write generation, then search the page.

It occurs to me we should probably have a memory barrier instruction after we copy the write generation, otherwise the compiler might re-order that read after we've actually searched the page? (Or make page->write_gen volatile?)

--keith

related to

WT-1 placeholder WT-1

Closed

WT-2 What does metadata look like?

Closed

WT-3 What file formats are required?

Closed

WT-68 Design and implement dump format

Closed

WT-103 --enable-python requires --enable-shared

Closed

WT-175 race in forced page eviction

Closed

WT-179 the cache isn't empty after verifying WiredTiger.wt

Closed

WT-310 overflow blocks may be accessed after deletion

Closed

WT-322 table and lsm object statistics

Closed

WT-403 Minor changes to fix uri table display. WT-397

Closed

WT-441 Allow LSM trees to discard the btree handle from the active chunk.

Closed

(6 related to)

Assignee:: Keith Bostic (Inactive)
Reporter:: WiredTiger
Votes:: 0 Vote for this issue
Watchers:: 0 Start watching this issue

Created:: Jan 31 2012 05:32:30 PM UTC
Updated:: Apr 16 2015 06:32:00 PM UTC
Resolved:: Apr 09 2015 01:06:15 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates