What problem does your feature solve?
Currently, we pass at start ledger to the indexer service. Whenever we update image, or redeploy it will start from given start ledger, which is usually genesis ledger.
Or if not, developer finds max ledger sequence already loaded into postgres and then use that as the start ledger.
What would you like to see?
We want this ledger sequence to be dynamically calculated by querying postgres DB. So even if developer sends genesis ledger sequence (say 2) as start day, the program finds max ledger sequence from postgres and use that as starting point.
What alternatives are there?