> Another option is to keep our heap table structure intact, and just
> Sleepycat DB for our indexes.  That may be a big win, with little
> downside.  Certainly something to think about.  It may work 
> better with MVCC, and allow fast sequential scans and fast heap
> access from the indexs, without having to go through the db structures
> to get to it.

But... we will still have to implement new smgr for tables and
redo/undo functions for heap access method.

Vadim

Mon, 15 May 2000 13:39:41 -0700
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: Proposal: replace no-overwrite with Berkeley DB