Postgres will outlast your framework, your ORM and possibly your company.
Reliability compounds
Established relational databases solve transactions, constraints, indexing, backups and recovery with decades of operational knowledge. For many products, that foundation is more valuable than a specialised feature used by a small part of the workload.
Boring does not mean obsolete. It means the team understands failure modes, can hire for the skill and can obtain support when behaviour becomes unexpected.
Earn additional systems
A new database introduces another security model, backup process, query language, deployment path and consistency boundary. Add it when measured workload requirements cannot be met reasonably by the existing platform.
Prototype with representative data and failure tests. Benchmark the hard query, recovery procedure and operational workload, not only an idealised read path.
Keep data ownership simple
Choose a clear system of record and derive search indexes, caches or analytics stores from it. Define how derived data is rebuilt and how freshness is communicated.
The database decision should preserve optionality. Standard interfaces, exportable data and documented migrations reduce the cost of changing direction later.