My guess is that Postgres would be better to start with.
Elasticsearch is awesome at natural language-ish searching, filtering, and aggregations on large amounts of data. However, unless your app has a strong need for one of those you'd probably get better value out of a relational database because they are so flexible, and I would guess the integrity and relational aspects will be much more useful for you.
I'd wager that most companies who run Elasticsearch also run a relational db, but the converse is not true.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My guess is that Postgres would be better to start with.
Elasticsearch is awesome at natural language-ish searching, filtering, and aggregations on large amounts of data. However, unless your app has a strong need for one of those you'd probably get better value out of a relational database because they are so flexible, and I would guess the integrity and relational aspects will be much more useful for you.
I'd wager that most companies who run Elasticsearch also run a relational db, but the converse is not true.