model-writtenrun 9121 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Jeff Janes opened the thread by reporting confusing JSONPath examples, unclear operator descriptions and an unhelpful claim of full SQL-engine integration; after finding the query functions, he suggested separating the path language documentation from the SQL operators that invoke it #1 #2.
- Alexander Korotkov proposed complete SQL examples or an explanatory note, clarified the operators, and suggested consolidating the path language documentation in the datatype chapter #3.
- Tom Lane opposed putting detailed functional behavior in the datatype chapter and wanted JSONPath after the ordinary JSON functions, possibly in its own section; Alexander then supported consolidating the language description there with only a brief datatype entry #4 #5.
- Steven Pousty advocated separating datatype definitions from ways of manipulating JSON data, while Alexander explained that PostgreSQL follows SQL:2016 and distinguished SQL-level functions from constructs inside a jsonpath value; their exchange also identified an ISO technical report as a useful public reference #6 #7 #8 #9 #10.
- Peter Eisentraut proposed simply swapping the two subsections, following the regular-expression documentation's functions-first organization #11.
- Liudmila Mantrova submitted that narrower change for PostgreSQL 12 together with the sentence clarification, leaving a separate top-level section as a possible future improvement when more SQL/JSON functionality arrived #12.
- Peter committed the reordering with light editorial changes as a083657896, then committed the exact sentence correction separately as a4a5c0cf9c, both drawn from #12.
- Peter confirmed completion in the final reply #13; both submitted changes landed, while the broader consolidation and expanded examples discussed earlier were not included.