I don’t think postgres has that tho? It has support for SQL2016’s jsonpath, but those are string queries, not sql-level traversal.
SELECT t->'j'->'foo'->'bar'->2, ... FROM tbl t ...
After all if that’s your benchmark every database with a TEXT type already has T081.
The syntax is different, but close.
SQL 2023: SELECT a.key
PostgreSQL 9.3: SELECT a->'key'
PostgreSQL 14: SELECT a['key']
Don't get me wrong - I love the feature and use it a lot, but I find the syntax awkward and honestly just... strange (though I've not researched it and have no idea of the reasoning behind it).
Will postgres adopt the SQL standard for JSON "simplified accessor" syntax? Has there been any statements or communications from the development team?
I'm pretty sure the syntax was just reused from hstore (https://www.postgresql.org/docs/current/hstore.html), for familiarity and simplicity. hstore predates json by 4-5 years.
It might also have made expressions easier to parse, as it doesn't conflict with normal identifier access.