Ford
There is a potential alternative approach where the indexer-agent code is updated, so that multiple indexer-agents can be operating with a shared backend. I personally think that approach would be...
Thanks for thinking through it @hopeyen! I agree with your conclusion; it was what I had intuitively assumed, but I really appreciate you going through the detailed comparison to confirm.
This is currently setup to emit a warning, but I'm now thinking we should fail the subgraph on this condition. Thoughts?
Suggestion: query the model when executing command, if only one value for network identifier than don't require the user to supply the --network param.
I believe we rely on the PSQL DBs table statistics, so the counts will not be perfect.
Honestly not sure if this is a bug or a feature request, but it definitely looks worth supporting. We'll take a look.
@PaulRBerg yeah that was the intention ("outdated"), I haven't been using the specific types of "closing" yet sorry if that was confusing. I did a big pass yesterday to categorize...
`--postgres-url` startup param works on my end 🤔 . Closing this issue as it's a bit old
@PaulRBerg does the `or` nested under an `and` in your most recent comment address your use case? So it works essentially, but more clear documentation and error messaging would help?
Agreed, not even a little bit informative. I'd think we could detect this `or` usage and suggest something in the error message, though pointing to a readme in the repo...