My general rule of thumb is "Use Postgres until you've discovered why you can't use Postgres."
Anything you introduce is another moving part you have to operate and maintain, and in the beginning, Postgres can probably handle it. Wait for load, see where its failing, and then you'll have a better idea if adding another tool is worth the cost.
The issue with this general rule of thumb is that we can swap Postgres for many others, including non-relational, and it works.
Another rule of thumb. Use what you are comfortable with until it stops doing what you want.
Doesn't the same argument apply even more to using SQLite instead?