> > we talking about output - I can imagine, so there is only two possibilities > > - plain join, and pretty formatted join (but with only one style). > > This makes sense. Postgres core really only needs to support the > minimum styles necessary for core requirements. This means raw > unformatted json for data productions to client and an appropriate > formatting for explain. Fancier stuff like a generic formatted is > fine but those features *belong in an extension*.
The thing is - it's not only about whitespace, otherwise I would probably not bother with the generic interface. For my original problem, there is simply no way to do this correctly in an extension w/o copying over all of the logic from json.c, which I have to do right now, would rather not.
I am sorry - we are talking about JSON, not about any styled document. I disagree, so it has not be implemented as extension - the backport of JSON support is a extension.