It is now, but before it had that privilege, MySQL did. The hype he is referring to may have taken the crown off MySQL and given it to PostGres. But make no mistake....postgres is not water. How do i know? Because it, too, will one day be unseated. And water does not lose its crown.
We're seeing the same thing in programming language adoption, where TypeScript is exploding in popularity and seemingly every language is getting static types if it didn't already have them.
To me, the rise of Postgres (and its spiritual siblings, languages with expressive, static type systems) are about maturing of the industry rather than hype.
And good documentation. Very good documentation.
SQL has been the default for eons, (although I still use a 70s era heirarchy based database on a daily basis), but that is another story. My company has dozens of large production scale databases and I think only one or two NoSQL products. We don't use Postgres unfortunately though.
NoSQL went through a hype in some circles (stayed non-existent in mine for the most part), but in my eyes, SQL has always been the work horse and was never not the default in the greater industry in my eyes. The Postgres implementation has become pretty popular recently, but so has Oracle and others in the past.
I think the commenter was getting at this.
Your file system perhaps?
"Bucardo is an asynchronous PostgreSQL replication system, allowing for both multi-master and multi-slave operations"