Thanks Alvaro. Looks cool. So, on the one hand it'd be nice to be able to auto-generate this once all the commands are standardized into one structure. That'd be slick.
On the other hand, the number of commands in SQL is not that large a universe, such that it'd be at least somewhat practical to just add Output as a standard section of the doc page for any command. They number 182 in both v11, v12 and v13 thus far, and many of those are variations of ALTER, CREATE or DROP (127 of them, in fact), such that they probably mostly share an output format. More importantly, the output of each command is unlikely to change much going forward, certainly not within a major release (right?). So we could just document each command's output, and if need be then pull that information into a summary page thereafter, or when the commit you mention is finished.
Just seemed like a standard thing that software docs cover - like how the documentation of a programming language's function library always mentions what is returned by each function (even if nothing).
I think starting with commit 2f9661311b83 it might be possible to create such a table. I'm wary of documenting this painting us into a corner forever, though.
