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

From Ron Mayer
Subject Re: YAML Was: CommitFest status/management
Date
Msg-id 4B16B1A9.4030407@cheapcomplexdevices.com
Whole thread Raw
In response to Re: YAML Was: CommitFest status/management  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: YAML Was: CommitFest status/management  (Brendan Jurd <direvus@gmail.com>)
Re: YAML Was: CommitFest status/management  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> YAML...
> 
> Hmm.  So the argument for it is "let's make a machine-readable format
> more human-readable"?  I'm not getting the point.  People should look
> at the regular text output.

IMHO YAML beats the regular text format for human-readability -
at least for people with narrow terminal windows, and for novices.

Greg posted examples comparing regular-text vs yaml vs json here:
http://archives.postgresql.org/pgsql-hackers/2009-08/msg02090.php

I think it's more human-readable for novices since it explicitly
spells out what values refer to startup values vs totals.
I think it's more human-readable to me because the current text
format frequently wraps for me on even a modestly complex query,
and I find scrolling down easier than scrolling both ways.

None of the other machine-intended formats seem to suit
that purpose well because they're dominated by a lot of markup.

That said, though, it's not that big a deal.




pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Hot Standby remaining issues
Next
From: Robert Haas
Date:
Subject: Re: Page-level version upgrade (was: Block-level CRC checks)