On 06/26/14 22:52, Nikolay Samofatov wrote:
You know that it is used to store intermediate RecordBitmap's during index
retrieval operations.
This is very performance sensitive code, and this implementation outperformed
and used less memory
than older SBM-based implementation.
I remember
27.06.2014 16:52, Jesus Garcia wrote:
The phantom TransactionID appears after one commit retaining of one
transaction.
Commit retaining internally creates a new transaction (with new ID),
hence your phantoms. I think we should add the new ID to trace output
for commit/rollback retaining.
On Jun 23, 2014, at 3:57 PM, Nikolay Samofatov
nikolay.samofa...@red-soft.biz wrote:
Some records for a join can be read before a transaction is committed, and
some after. Same with EXISTS. It can see different set of commits from the
one when main row was read.
You can see partial
Provide compiler warning in case when there is EXCEPTION command WITHOUT name
specified OUTSIDE handling block
--
Key: CORE-4474
URL:
