You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to have an estimate of time remaining when running the indexer. Currently only the rate of indexing (records per second) is reported, but if possible, the estimated remaining time based on rate * total number of records to index would be helpful.
The text was updated successfully, but these errors were encountered:
postgres keeps table statistics (for query planner) that have numbers that are generally going to be on the same order of magnitude as the table count.... so that might work for a time estimate.
Actually, with newer postgres features such as Parallel Seq Scan, the time to compute count(*) is much faster than before, definitely fast enough to work for this use case.
It would be useful to have an estimate of time remaining when running the indexer. Currently only the rate of indexing (records per second) is reported, but if possible, the estimated remaining time based on rate * total number of records to index would be helpful.
The text was updated successfully, but these errors were encountered: