Some years ago I mailed patches out to someone regarding
Berkeley DB 1.85 btree problems. The two issues which come
to mind are...
1) The page split position is improperly computed.
This can cause corruption when a very full
page has an item which is very large inserted onto it.
The
Jeff Anton wrote:
Some years ago I mailed patches out to someone regarding
Berkeley DB 1.85 btree problems. The two issues which come
to mind are...
1) The page split position is improperly computed. ...
2) The record put code has a last page put to member ...
I'm going to have to dig up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Anton wrote:
[...]
| I'm going to have to dig up these fixes, but presuming
| I do, who should be alerted? Just file a bug? Recreation
| is extremely difficult.
I think Oracle is maintaining a webpage about their known bug/fixes here:
3 matches
Mail list logo