Hey Pavel,
I went back and looked at the source here. It appears that 24MB is the
expected size for an index file -- each entry is 24 bytes and the index
file should keep 1M entries.
That said, for a "cold tablet" (in which you'd have only a small number of
actual WAL files) I would expect only
Hi Sergey,
The optimization you're looking for is essentially to realize that IN-list
on a primary key prefix can be converted as follows:
scan(PK in (1,2,3)) ->
scan(PK = 1 OR PK = 2 OR PK = 3) ->
scan(PK = 1) union all scan(pk = 2) union all scan(PK = 3)
Currently, the tserver doesn't support
