1 - At the start of your project's life, you'll want it because it's free as in beer. Except for ease of developping (where Postgres is also great), nothing else matter.
2 - Later, when you need some performance, even if you have a usage patter where Postgres is slower, you'll discover that the price of any of the other DBMS is highter than just adding hardware. Thus, free as in beer wins again.
3 - If you get huge, you'll discover that free software is a big deal, and the limitations of the proprietary DBMS add a huge amount of drag. Free as in speech wins now.
If I get to a point where I actually need the features, that SQL Server or another commercial RDBMS has, then I have a good problem. It means my business is doing well and I may be in a position to consider a changeover.
I used to fret about features that frankly don't really matter when you are starting out. Coming from an Oracle and SQL Server background, I wouldn't touch MySQL but Postgres hits the 80% mark quite easily.
Posgresql is free software.
And therefore for example no company can force you into their lock in for their profit and your loss.