lots of answers... Christoph Kiehl wrote:
Ok. To get this working, you have to create at least one segment per transaction, right?
not necessarily. as an optimization the current implementation uses the redo.log to keep track of index modifications that were only done in memory. this means that at the end of a transaction there won't necessarily be a new index segment on disk.
And index merging could be done in background?
index merging *is* already done in the background.
Sounds really interesting. But if the blob values are cached locally they have to be downloaded on startup first before the index starts to be fast.
correct.
Or does the blob cache survive restarts?
no, it doesn't. regards marcel
