Hello hackers, I’d like to propose an optimization for index creation on large tables. Currently, when creating multiple indexes on the same table, each index is built independently, triggering a full table scan per index. This leads to significant redundant I/O, especially for very large tables. F
Hi Ildar,
> I’m curious:
> - Has this been discussed before?
> - Are there any technical reasons why this wouldn’t be feasible?
> - Would such a patch be of interest to the community?
This might be a promising area for research. I suggest starting with
figuring out where exactly the bottleneck is
