Re: YAML Was: CommitFest status/management - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: YAML Was: CommitFest status/management
Date
Msg-id 20091207103416.9513.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: YAML Was: CommitFest status/management  (Josh Berkus <josh@agliodbs.com>)
Responses Re: YAML Was: CommitFest status/management  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> wrote:

> Having compared the JSON and YAML output formats, I think having YAML as
> a 2nd human-readable format might be valuable, even though it adds
> nothing to machine-processing.

Sure. YAML is human readable and can print more information that is
too verbose in one-line text format. +1 to add YAML format to EXPLAIN.

> Again, if there were a sensible way to do YAML as a contrib module, I'd
> go for that, but there isn't.

Some ideas to export formatters:1. Provides register_explain_format(name, handler) function.   Contrib modules can
registertheir handlers when LOADed.
 
2. Provides a method to specify a filter function. XML output is   passed to the function and probably converted with
XSLT.

BTW, an extensible formatter is surely useful, but what will we do about
XML and JSON formats when we have it? Will we remove them from core?
If we have a plan to the direction, we should complete it before 8.5.0
release. We will be hard to revert them after the release.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: Syntax for partitioning
Next
From: Robert Haas
Date:
Subject: Re: YAML Was: CommitFest status/management