Postgresql has had views for quite some time. they can be made updateable via user triggers, but simple updateable views are not implemented automatically like the spec says they should be.
That said, I've never used a simple updateable view, there's always been more to it than that, so no great loss there.
also unions, user defined functions (in about 12 languages) subselects, transactions, constraints, etc... etc...
Incredible amounts of optimzation has gone into the cost based query planner in the last year.
MySQL: content storage with good speed but poor relational integrity constraints.
Postgresql: Relational Database with full integrity built right in. Used to be a bit pokey, but is now doing quite well, and especially good at handling high parallel loads.