> But as Vik said earlier, maybe it's not worth it to provide a markdown > output as pandoc can generate the markdown from the HTML output. > And if you need the markdown output to generate HTML why don't you use the > HTML output ?
The round-trip through pandoc does not do any miracle. The end result is readable to the human eye but structurally broken. If converted back to html, it's no longer a table.
Anyway I tend to agree with Vik on this: "Markdown isn't standardized enough to support and please everyone."
Now that we have csv as an output format, we can suggest custom csv-to-markdown converters to produce markdown rather than implementing one particular flavor of markdown in psql, or several flavors through flags. The popular script languages have solid CSV parsers that make this relatively easy and safe.
I agree with you about importance of CSV. On second hand, I don't see a reason why we should not to support some very popular markdown formats - although there can be a discussion - which
maybe github and JIRA, CONFLUENCE
Regards
Pavel
Personally I'd use Perl with something like below, which looks short/simple enough to be shared on wiki.postgresql.org, along with versions in other languages.