Open timothy-e opened 4 months ago
I'll pick this one up!
Hey @timothy-e, I've been looking into this and am getting stuck. I took a look at calculate_table_size
because you mentioned similar changes could be applied in calculate_indexes_size
. I see in calculate_table_size
there's methods called like, YBCPgGetTableDiskSize
that make it straightforward to get the table size from DocDB, but can't seem to find a parallel for indexes.
If you have time, could you help point me in the right direction? I'm very new to this, so I apologize if there's something obvious I'm missing
hey @Pedja-Djape I too glanced the issue and your comments.
Afaiu (as far as I understand) functionality similar to CatalogManager::GetTableDiskSize
needs to be added in the YB catalog manager for getting index size and invoked in the calculate_indexes_size then.
@timothy-e can u help us verify our observations.
Jira Link: DB-12121
Description
pg_total_relation_size
should return the size including index size.We modified
calculate_table_size
to work for YB in D17169 / 2e767c443d80ac1144bfe75739dff84801f763b0.However, we missed modifying
calculate_indexes_size
, so it tries to check how much space an index is occupying on the local disk, instead of requesting the size from DocDB.A similar fix would probably work here.
Issue Type
kind/enhancement
Warning: Please confirm that this issue does not contain any sensitive information